From Vision to Growth.
An independent practice. Brand, product, internal systems, and the growth work after launch.
Not a site. A system.
A page is a surface. A business runs on what sits under it.
Ideas become products. Products become businesses. Businesses that grow.
The person who defines the problem is the person who builds it. The same person reads the numbers after launch. Nothing gets handed off, because there is nowhere to hand it.
That is the difference. The rest of this page follows from it.
Four kinds of work
Work here lands in one of four kinds.
-
01
Brand and identity
Name, voice, and the way the business looks when someone meets it first.
-
02
Service or app
The thing your customer uses. Screens, flows, and the logic behind them.
-
03
Internal systems
The tools your team uses to run the day. Admin, records, and process.
-
04
Growth operations
What runs after launch. Analytics, automation, content, and the changes the numbers ask for.
Name the closest one in the first message.
Five stages, one line
The work moves along one line. No stage changes hands.
-
01
Discover
I find out what the business needs, before design starts.
-
02
Strategy
I fix the scope here. What to build, and what to leave out.
-
03
Design
Structure first, then surface. You see it before I build it.
-
04
Build
Building starts after the scope settles, not before.
-
05
Grow
Launch is a stage, not the end. I stay on the numbers.
The line starts before there is a brief. It ends after the thing is running.
The line does not break between stages.
How it starts and what stays
The parts that matter are the start, the changes, and what stays after.
-
01
After launch
Launch is not the end of the arrangement. The Grow stage runs after the thing is live.
-
02
When scope changes
Scope changes. When it does, you talk to the person who set it. No change request travels through anyone else.
-
03
What you can hand on
What I build stays in a form someone else can pick up. Running cost is part of the choice, not a surprise after launch.
Before you decide, read where this stops.
One system, still running
SONA CRM is my own product, not client work. It is here because the whole span is visible in one build.
What it was built for
Customer lists lived in spreadsheets. The same name got assigned twice and yesterday's file overwrote today's. Leads were split by hand, and the settlement was recalculated every month.
One flow, four steps
A request comes in and is routed to one person. It moves through the sale, then the activation. The settlement calculates itself from what was already entered.
Nothing is entered twice. Each step reads what the step before it wrote.
-
01
Step one, a request arrives and is split by rule
-
02
Step two, the request lands with one person
-
03
Step three, the sale moves from pending to activated
The same screens on a phone, the same data
-
04
Step four, the settlement calculates itself
Screens shown with demo data
Still running
There is no handover date on it. It is live at sona.im. The same person who built it runs it.
What one build can show
One build is one build. It does not stand in for volume.
What it shows is span. One person defined the problem, designed the flow, and runs the result.
The same four steps, screen by screen.
See it running sona.im, in a new tab.
sona.im is the product. This page is the practice behind it.
Where this stops
The structure that removes handoffs also sets limits. Three of them.
-
01 Timing decides more than budget
There is a ceiling on how much work runs at once. Client work is not the only thing under it. SONA CRM runs there too.
So the start date is a real constraint, not a formality. If your date is fixed and close, say it in the first message.
-
02 Some work belongs elsewhere
Work that needs standby coverage around the clock does not fit here. Neither does a build that has to run on parallel tracks at once.
If that is your situation, an in-house hire or a firm with shifts is the right answer.
-
03 If I stop, the work stops
A single line has a single point of failure. If I stop, the work stops that day.
The repository, the accounts, and the domain are in your name. Access does not stop with me.
If any of this rules the work out, better to know now than after a contract.
Three other ways to do this
Each one is right in some situations. Here is what changes.
-
A web production firm
The difference is structural. In a firm with a sales function, the person who pitches is not the person who builds. Here you talk to the person doing the work.
-
Development outsourcing
The difference is where responsibility starts. Outsourcing answers for meeting the spec.
If the spec is wrong, that loss is yours. Here defining the spec is part of the work.
-
An in-house hire
The difference is fixed against staged. A hire turns a changing need into a fixed cost and a fixed role. What a project needs changes from stage to stage.
| Axis | A web production firm Right when the spec is settled and the schedule is short. | Development outsourcing Right when the requirements are already correct. | An in-house hire Right when the work never stops. Standing work wants a standing role. | SONA |
|---|---|---|---|---|
| Who you talk to | Who you talk toSales, then a builder | Who you talk toA manager, then a builder | Who you talk toThe person you hired | Who you talk toThe person doing the work |
| Where responsibility starts | Where responsibility startsAt the brief | Where responsibility startsAt the spec | Where responsibility startsAt the role | Where responsibility startsAt the problem |
| Fixed or staged | Fixed or stagedFixed scope | Fixed or stagedFixed spec | Fixed or stagedFixed cost and role | Fixed or stagedStaged |
| Time to a first deliverable | Time to a first deliverableShortest | Time to a first deliverableShort | Time to a first deliverableLongest, hiring comes first | Time to a first deliverableLonger, definition comes first |
| Work running at once | Work running at onceParallel tracks | Work running at onceParallel tracks | Work running at onceGrows as you hire | Work running at onceCapped |
No column wins every row.
The rest of the questions
The hardest ones are at the top.
What happens if you go quiet mid-project?
The work stops until I am back. That is why nothing sits in a place you cannot reach. You can hand the current state to someone else without waiting for me.
Does your own product take time away from client work?
It does. SONA CRM runs under the same ceiling as client work. That is why the start date is the first thing I ask about.
Can you handle a large project?
Large is not the problem. Standing coverage and parallel tracks are. If the work splits into stages that each finish, the total scope is workable.
When is this the wrong choice?
When the work never stops and needs someone on call. When the schedule is fixed and cannot move. In both cases a hire or a firm with shifts fits better.
Who owns the code?
You do. The repository, the accounts, and the domain sit under your name from the start. I hold nothing back to keep you tied in.
What if the direction changes halfway?
Then the scope changes. You raise it with the person who set it. If a change moves the schedule, you hear that before it starts.
Does the work continue after launch?
Yes. Grow is one of the five stages, and it runs after the thing is live. What that stage covers gets decided with the scope, not after it.
Could a website builder do this instead?
If you already know what to build and it is a few pages, yes. A builder makes things fast. It does not decide what to make.
Can you start from a rough idea?
Yes. Discover is the first stage, not something you bring with you. A rough idea and a real constraint are enough to start.
What do you need in a first message?
What the business does, what is stuck, and when you need it running. That is enough to answer whether this fits. Documents can come later.
Tell me what is stuck
The first message decides whether this fits. Keep it short.
-
01What to include
Bring what the business does, what is stuck, and when you need it running.
-
02What comes back
You get one of two answers back: this fits, or here is why it does not.
team@sona.im
It goes to the person who would do the work.