One scoped site, operated from source you own.
I scope the pages and the job the site has to do. Then I build a Next.js or marketing site, review what ships, and leave the source with you. This site is the live example: I operate it.
$650
One scoped Next.js or marketing site.
Request a fit checkNo-charge fit check before access or work. If it fits, the fixed scope and price are confirmed first.
Stages
Open each stage to see the work product. The exact scope is set only after the evidence is reviewed.
ScopeName the pages and the job.
Write the page list, the job each page has, and the stop condition. Work does not start until that scope is agreed.
Output: a written site contract.
BuildImplement the agreed site.
Build the Next.js or marketing site inside the named scope. I use the same public visual language already on this site unless the contract says otherwise.
Output: source in a repository you own.
ReviewI review what ships, then you own it.
I check the site against the contract, make the named revision pass, and leave the source with you.
Output: reviewed source plus the revision record.
What is included
- One named site scope: pages, job, and stop condition, written first
- A Next.js or marketing site built inside that scope
- Source you own, plus one named revision pass after I review what ships
I do not promise App Review approval, ranking, downloads, or revenue. The written scope decides the work.
Fit
Good fit
I scope the pages and the job the site has to do. Then I build a Next.js or marketing site, review what ships, and leave the source with you. This site is the live example: I operate it.
I scope the work, review what ships, and you own the source.
Not included
- An unbounded product, a content mill, or Android work
- A prompt dump with no scope, no review, and no source transfer
- Ranking, traffic, or revenue promises
Request
Request a fit check
Send the project name, the page list you have in mind, and the job the site has to do. I will reply with whether it fits this engagement.
Do not submit passwords, API keys, tax or identity documents, or private customer data. Sensitive access is never requested in the first message.