How a build runs
A workspace should be understandable the day it arrives and still useful a year later. The process keeps scope, access, and limits visible from the first conversation, and the pace of deciding stays with you.
The four phases
1. Intelligence brief
We start with a conversation about the work that repeats and where it stalls. I then document your offers, prices, voice, tools, constraints, and recurring work in a written brief. You review it and correct anything I got wrong.
2. Architecture
The design names every component, what each one connects to, what access it has, and where a person approves. Price, timeline, and exclusions are written down. Any change in scope is priced and approved before work continues.
3. Build and test
Each component is built from your real examples in Civic North's testing workspace and tested against the standard you set, including the places where a person must review.
4. Delivery
Before handoff, the workspace passes a security check of your account settings and a set of acceptance tests. It is installed with you, in your account, with a plain-language guide for every skill and training on live work. A 30-day check confirms it is being used and understood.
Civic North is one person by design, and I take two builds at a time so each one gets full attention. When you are ready to begin, we agree on a start date that fits your work.
What every build includes
Written scope
A named list of components and exclusions, agreed before work begins. No mystery deliverables.
Tested on your work
Representative examples from your practice are the test set. A skill is done when it handles your real inputs to your standard.
Human review points
Every workflow names where a person approves. Drafts never send themselves.
Guides you own
Every skill ships with a plain-language knowledge guide. When something changes, ask the workspace to update the guide, or edit it yourself.
Access, credentials, and your data
Civic North never holds a client password. Not for your workspace, not for your email, not for any tool connected to the build. Every sign-in is done by you, on your own account. If you are ever offered a shortcut that involves handing over a login, this is not it. Installs are by video call.
Team plans: tested first, then installed with you
Your workspace is built and tested first in Civic North’s own testing workspace, using your materials. Then we install it together in a scheduled, screen-shared session where you are the one logged in. You make every click yourself, including every tool connection, such as Gmail, Google Calendar, Google Drive, or Notion, and scheduled task setup, following the folders and instructions emailed ahead.
Solo clients: tested first, then installed with you
Your workspace is built and tested first in Civic North’s own testing workspace, using your materials, so we can confirm it works the way it will run for you. Then we install it together in a scheduled, screen-shared session where you are the one logged in. You connect your own tools, such as Gmail, Google Calendar, Google Drive, or Notion, through their usual sign-in screens while I guide you through each step.
Your materials, handled plainly
Sensitive test material is anonymized where the content allows. Test copies are deleted from the testing workspace at handover. Your materials are used for your build and testing, and for nothing else.
A written record, every time
Every install ends with a short written record: what was installed and what it connects to. You keep that record.
Install, scoped to the build
Every build includes a guided install, until you can use the workspace yourself on live work. How many sessions, and how long they run, are set in your written scope, based on how many skills are in the build, how complex the workflow is, and how much live practice you need. Additional sessions, if you want them, are scoped and priced in the proposal, not sold as a fixed menu on this site.
How payment works
Payment terms are set out in writing before work begins.
Every engagement starts with a written scope note. The Sprint is paid in full to begin. Builds are paid half to start and half at handover. Flagship builds are paid in milestones across the build. Payment plans are available on projects over $1,000. Payment is by card or bank transfer through a secure Stripe invoice.
Where judgment stays human
A workspace can prepare, organize, draft, and structure work. It can also be wrong or incomplete, so you remain responsible for reviewing output before it reaches a client. Sensitive client records stay out by default. Civic North never asks for your passwords, and each component receives only the access its job requires.
Not sure which engagement fits?
Describe the work you want help with, in your own words. The first conversation defines the starting point.
Start a conversation