The short answer
It starts with an online call, then a plan, then the work, then a check and a go-ahead from a person. You see it and approve it before it goes live.
The steps differ a little for a Growth Engine and for an app. The shape is the same.
The shape of every project
- Talk. A short online call with our founder about your business and what's in the way.
- Plan. Avery turns that conversation into a plan you can read.
- Build. The chicks do the work, each in their own role.
- Check. People review the result, and you do too.
- Go live. Nothing is released until a person says it's ready.
For a Growth Engine
After the call and the plan, Sage defines your ideal buyer and builds the target list. Marlo writes your offer and your messages in your voice.
Then you approve everything. Nothing is sent until you do. Once your engine is live, it finds buyers, contacts them, answers the easy replies, and books calls on your calendar. You take the calls.
You'll get 30-minute check-ins while we build, and a one-page report each month.
For an app
The app goes through five stages: Discovery, Analysis, Create, Test, and Ship. Wren gathers the requirements, and the builder (Lyra for web, Mae for mobile) writes it. Sloane reviews the code and Robin tests it like a real visitor.
Our founder approves every build before it ships. Then the cycle loops back for the next round of fixes and features.
Where you come in
- At the start, to tell us what matters.
- At the plan, to say yes or change it.
- At the check-ins, to adjust as we go.
- At the end, to approve what goes live.
Between those, you can get on with your week.
How long it takes
It depends on the project, and we won't invent a number here. A simple Growth Engine goes live faster than a custom app, and we'll give you a real estimate on the call.
What can slow it down
Waiting for decisions is the usual cause. If it takes two weeks to answer a question, the project takes two weeks longer. We'll tell you plainly when something is waiting on you.
The longer version
If there's one habit that keeps projects smooth, it's agreeing early on what done looks like, since a clear finish line lets every stage check its own work against something real, and it lets you say yes to a plan with confidence rather than discovering at the end that you and the team imagined different results. Decide done first. Then build toward it.
Projects stall most often at the handoffs between steps, when one person assumes another has the answer, and that's the reason we write the plan down in plain language that you can read, correct and approve before work starts, so that every later question can be checked against a page rather than against anyone's memory of a call. Written plans help. So do short check-ins.
Keep reading
- Who will I talk to, and how often?
- What if I want to change something once work has started?
- Back to the homepage
Book my call
A short online call. This is step one, and you'll leave with a clear idea of what step two looks like for you.