Running a client project in the portal

A client project on Kabbes Development is a page in the client portal that both sides share. Staff with the client-portal ability see every project; the client sees their own. Everything about the build lives on that page: the agreement, the previews, the build log, the files, the messages, the invoice. This guide walks the project from creation to handover.

1. Create the project and grant access

New project, the client’s business name as the title, a one-line description of what is being built. Grant access to the client’s email. If they have no account yet, the invite creates one and the project is waiting when they sign in.

2. Run the agreement wizard

Documents → New agreement. Pick the type (a custom build, a care plan, a change order, a template license, or write your own), answer what it asks, review the generated document, and create it. It lands as the agreement page, the share link, and, when you tick it, the price and invoice lines on the project. The client signs with a typed name. Every agreement is signed for Kabbes Development by Jackson Kabbes, Founder & CEO; your name shows as the person who prepared it.

3. Keep the build log honest

Every drop, every milestone, every decision goes in the build log with a line the client can read. Set the work status so the project page says what is happening right now. A client who can see progress does not write to ask about it.

4. Files, previews, messages

• Files: logos, copy, photos, PDFs. Upload theirs and yours; everything is dated and named.
• Previews: the design direction and every page after it show as live previews on the project page, not screenshots.
• Messages: project threads keep the conversation next to the work. Reply there rather than by email so the record is complete.

5. Invoice and status

The invoice lines come from the agreement; add items only for agreed extras. Mark the project purchased when the balance clears, and move the status through active, review and complete as the build moves. The client sees each status change.

6. Handover

At launch the client owns the site outright: the source, the accounts, a walkthrough, and a written guide to deploying it anywhere. Put all of it on the project page before you call it complete. The public "How a build works" page describes the whole process in the client’s words; it is linked from every agreement.