The build
Kickoff, access, technologies and the as-built record.
The engagement's Build tab keeps the working records for the build. It's deliberately light: the app holds the summary and the status, and the detail lives in your own folder and tools.
Documentation. Link the shared folder (Google Drive, SharePoint, Notion…) where the build's scripts, prompts, diagrams and handover notes live. Only your team sees the link.
Kickoff checklist. Start kickoff copies your checklist (Settings →
Process → Build kickoff checklist) into the engagement. Each item is either
the client's ("Give us access to those systems") or yours ("Book the kickoff
meeting"). Starting it adds a Kickoff page to the client's workspace, where
they Mark as done their items with an optional note. You're notified
(kickoff.updated) and it shows under Needs attention. Tick your own items
Done or Not needed, add or remove items, and the Build tab's count shows
what's still open. With automatic reminders on (Settings → Notifications),
the client's main contact gets a reminder email listing their open items and
requested access, after the same number of days and up to the same maximum
as stakeholder reminders.
Access register. A record of which client systems you can get into: the system, the access level, the account used (e.g. a service account), where the credentials are kept (e.g. "1Password › Clients › Acme"), who granted it, a review or remove by date, and its status (requested, granted, revoked). It never holds passwords or keys: the app refuses anything that looks like one, on your side and the client's. Good practice:
- ask the client to invite your own login or create a service account, instead of sharing theirs;
- share any secret through a password manager (a shared vault, or a one-time link), never by email or chat;
- set a review date (the end of the build, or of the retainer) and mark access Revoked once it's removed. If it's still Granted the day after its review date, it shows under Needs attention (once; set a new date to be reminded again).
The client sees the systems you've asked for and why (not where credentials are kept) on their Kickoff page, and clicks I've given access when done.
Technologies used. Each tool the build runs on (n8n, Zapier, Claude, Supabase…): what it's for, which solution it serves, whose account it's on (the client's, yours or a third party's), a link to its docs, workflow or folder, the monthly cost and who pays it (the client, to the provider directly, or you, inside your monthly fee), and backup and recovery (what's backed up, where, and how to restore it). Each tool is Recommended (suggested, not confirmed), Chosen, or Replaced (swapped out, with why). The client sees only chosen tools: what each does and whose account it's on (no costs, links or notes) on Scope & build under What we built, so they know what they own at handover. Each solution's build guide uses this same list.
Build guide. Each solution on the Solutions tab has a Build guide tab next to Overview and Flow:
- Tools and technology: the AI recommends a stack (why each, the alternatives, cost and backup and recovery). Click Use it to choose one, or Replace… with a reason, then add what you used instead.
- How the systems connect: an architecture diagram with its Mermaid code.
- Build steps: step-by-step instructions with the tool and hours. Tick them off as you build, reorder, reword or add your own. The Process tab's Build stage shows "3/9 steps" for each item, with a link to its guide.
- Improve with AI keeps your chosen tools and steps and fills the gaps.
The solution workspace. Click Open on a solution (or its title) to work on it on its own page, with Previous and Next to move between them. The page has these tabs:
- Overview: edit the proposal (summary, how it works, numbers, plan, risks), or redraft it with AI. The flows and build guide are kept.
- Flow and Build guide: as above.
- Notes: a dated log of decisions and findings, for your team only.
- Ask: pick a person (the one who does the task is suggested), let the AI draft questions about what the build needs to know, edit them, and click Ask. The questions are added to that person's follow-up questions and emailed with their private answer link. Their answers show here and feed their interview's analysis.
- Build in n8n (when n8n is in Settings → Tools you know): the AI
recommends how to build it in n8n, or you choose:
- A workflow (the same steps every time): importable JSON. Copy it and paste it onto an n8n canvas, or download it and use Import from file. An AI Agent node inside it comes wired to its chat model and tools.
- An n8n Agent (it reads, decides and acts): the prompt for n8n's agent builder (start a New chat in n8n and paste it), or each field to fill in yourself (model, instructions, skills, triggers, tools, with the ones that need approval marked, and memory), plus knowledge files to upload on the agent's Knowledge tab. The files are written from the task, the build guide, your notes and the answers from the Ask tab; anything not known is marked [TO CONFIRM WITH THE CLIENT].
- Still to do in n8n lists the credentials, placeholders, approvals and tests. Lines starting with Check: are problems the app found in a workflow draft.
Technical documentation for the client. When you hand over, click Share with the client on a solution's build guide. Their Scope & build page then shows Technical documentation: how the systems connect, the chosen tools with whose account they're on and how to back up and restore each one, and the build steps without hours. They can print it or save it as a PDF for their business continuity and disaster recovery records. Passwords and keys are never stored: the app refuses anything that looks like one. If you sell the documentation as a deliverable, add it as a line on the quote.
As built. Solutions change as they're built. Each approved solution's record on the Process tab (Build stage) has an As built field: how it actually works now. The proposal stays as it was agreed. The client sees the as-built notes on Scope & build. The Build tab shows which solutions are documented.