The short answer
Tell us. The check-ins are there for exactly that, and your feedback goes back into the same process until it's right.
Changing your mind early costs little. Changing it late costs more, and we'll be straight about which is which.
When changes are easy
Early. Before anything goes live or goes out, almost everything can change.
- The wording of a message. A new tone, a shorter version, or a different opening.
- The buyer list. Add a type of business, or remove one.
- A design choice. Colors, layout, or the order of a page.
- A priority. What to do first.
You say what's off, and we fix it.
How feedback works
For a Growth Engine, you review the messages and say what to change. Nothing is sent until you approve it. The 30-minute check-ins are there to adjust the buyer list and the wording.
For an app, you review the finished work and give feedback. It goes back through the same process: our founder and the chicks revise it until it's right.
When changes get harder
After something has gone live, a change is a new round of work. It might be small and quick. It might touch a lot.
We'll tell you which, and what it involves, before we start. You don't get a surprise.
When a change is really a new project
Sometimes "just one more thing" is a different thing. Say you start with a booking app and then want payments, reports and a customer portal. That isn't a tweak.
We'll say so, and show you how to take it in order. Often it makes sense to launch the first part and add the rest next.
What we ask of you
- Say it early. The sooner we know, the cheaper it is.
- Say what's wrong, not only what you'd like. "This feels too pushy" is a great note.
- Tell us what matters most if you have to choose.
What we won't do
We won't lock you into something you've told us is wrong, and we won't hide the cost of a change. We also won't say yes to everything. A good "let's not" is part of the job.
The longer version
The best changes tend to arrive right after you've seen something real, such as a first draft of a message or a first screen of an app, because that's when an abstract plan becomes concrete enough to react to, and a reaction like that is more useful than an hour of imagining. Don't wait for perfect. React to what's in front of you.
Cost and timing change with the stage you're at, so we try to be specific about it as we go: a change at the plan stage is usually a conversation, a change during the work is usually a bit of rework, and a change after launch is a new round with its own estimate, and in each case you'll hear the effect before you commit to anything. No surprises on the bill. Ever.
Keep reading
- How does a project run from the first call to launch?
- What if I don't like the messages?
- Back to the homepage
Book my call
A short online call. We'll explain how changes work for your project before you start.

