Client Handbook
How a project runs, who is responsible for what, and what you receive at the end
What this page is
This is the documentation for working with us as a client: the delivery stages, the division of responsibility, and how to operate your site after handover. It is not product documentation, because we do not sell a platform. Project-specific instructions ship in the repository README for your project.
Delivery Stages
Each stage has a defined output, so progress is checkable rather than a matter of opinion
Intake
Clarifying questions, feasibility check, written scope and fixed quote
Goals, examples of sites you like, any brand assets and deadlines
A scope document and quote you approve in writing before work starts
Structure
Sitemap, page outlines, content slots, technical approach
Confirming the page list and supplying or approving copy
An agreed sitemap and content checklist
Build
Implementation, responsive layout, accessibility and performance work
Review of preview deploys and one consolidated round of feedback per stage
A preview URL that updates on every commit
Checks
Automated build, accessibility, performance and SEO audits in CI
Final content proofread and sign-off
Audit reports handed over with the site
Launch and handover
Deployment, domain and DNS setup, redirects, analytics, sitemap submission
Domain access, or authority for us to configure it on your behalf
Live site plus repository, accounts and credentials transferred to you
What You Receive
On final payment, everything below transfers to you. There is no component you must keep renting from us in order to keep the site running.
- ✓ Full source code and Git history in a repository you own
- ✓ Deployment configuration, so any developer can build and deploy it
- ✓ Domain, hosting, analytics and form accounts in your name
- ✓ The automated audit reports produced by the final build
- ✓ A short written guide to editing content and redeploying
Where AI is used, and where it is not
AI agents generate and refactor code, draft content, and run checks. That is how a small studio can deliver at this pace, and we would rather state it than hide it.
A person reviews every deliverable before it reaches you, and decisions about scope, cost and architecture are made by people. If you want to know which parts of a deliverable were AI-generated, ask and we will tell you.
Running the Site Yourself
After handover you are not dependent on us for routine operation
Editing content
Text and images live in the repository or in the CMS chosen for your project. Committing a change triggers a rebuild and redeploy automatically.
Running it locally
Install dependencies, run the dev server, and open the local URL. The exact commands are in the repository README for your project.
Deploying
Pushing to the main branch deploys to production; pull requests get their own preview URL. No manual upload step exists.
Asking for changes
Send the request by email or WeChat. We reply within 1 business day, and quote in writing if the change is billable.
Question not covered here?
Email mingxinai@agentmail.to and we will answer it and add it to this handbook.