Stage four
The half where the customers come from.
Almost everything in this category stops at "built" and calls it done. A built product with nobody looking at it is a hobby with a domain name. So the pipeline keeps going: a CRM waiting for the first conversation, a campaign that goes out, and a blog and social presence that start filling up the same afternoon.
This stage uses three more members of the family — iKonekt, clickSomo and FABLS — and it uses the same written description everything else was built from. Which is why the campaign's first line says what the site's headline says, and the blog plan argues the case the document argued.
The order matters. The CRM goes up before the campaign, because a campaign that generates replies into an unwatched inbox is worse than no campaign: it burns the one first impression you get and produces a folder of people who wrote to you and were ignored.
First
iKonekt:
somewhere for demand to land, with a name against it.
Every channel a customer might use arrives in one inbox, as a contact with a recorded source, an owner and a thread that starts at the first word they said. Chat, live chat, forms, the reach-me button, call-me requests, e-mail, phone, QR codes on anything printed.
Ownership on arrival
Every lead is somebody's job from the second it lands, not from the moment somebody notices it. The difference between those two times is where new products lose their first ten customers.
Source kept, permanently
Down to the individual flyer or link rather than "offline". A quarter later, "did the campaign work?" has an answer with a number in it instead of three opinions.
Through to the invoice
The pipeline runs from first contact to a paid invoice, KSeF included, so the first sale does not need a spreadsheet and somebody's accountant improvising.
A launch is not an announcement.
It is the first customer.
clickSomo:
the kickstart campaign.
A new product's problem is not conversion, it is that nobody knows it exists. clickSomo runs the first push across the channels people actually read: e-mail, SMS, push notifications, and — for the kind of business where it still works better than anything digital — printed letters.
They run as funnels rather than blasts, so the second message depends on what the first one did. Opened but did not click gets a different follow-up from did not open at all, and somebody who replied is taken out of the sequence entirely, because they are now a conversation in the CRM rather than a name on a list.
Written once, again: the campaign copy is generated from the same description as the site. Nobody has to re-explain the product to the mailer, and there is no version of the pitch that only exists in an e-mail somebody wrote at eleven at night.
- 1Day 0 — e-mailThe case, in six sentences, with the price in it. Short links, redirects counted, no tracker anywhere.
- 2Day 2 — branchOpened, not clicked → a second angle. Never opened → a different subject line, sent at a different hour.
- 3Day 3 — SMSOne message, to the segment that engaged. Quiet hours respected without anybody configuring them.
- 4Any replyLeaves the sequence, becomes a thread in iKonekt with an owner on it.
- ·What it does not doBuy a list. The audience is yours; the sequence is the part being automated.
E-mail · SMS · push · postTriggers, not blasts
- 1PlanA three-to-six month editorial plan, built from the written case and the words the product's buyers actually search for.
- 2WritersPosts drafted and published on schedule, in the brand's voice, with pictures that carry their licence.
- 3SocialsThe same plan pushed out to the accounts, at the cadence each one rewards.
- 4ReportsWeekly and monthly, saying what went out and what it did. Read in four minutes, not interpreted for twenty.
- ·Why now, not laterContent is the one channel whose payoff is on a delay. Starting it in month four means the payoff arrives in month ten.
Months, not intentionsSame voice as the site
FABLS:
blitzscaling the visibility half.
Blogging and social presence are the slowest-paying channels a new product has, which is exactly why they get postponed, and exactly why postponing them is expensive. The compounding does not start until the first post exists.
FABLS runs both automatically: a plan measured in months, writers producing the posts, the social accounts fed from the same plan, and a report each week and month that says plainly what happened. It starts on the same afternoon as everything else, so month four inherits three months of work instead of a resolution.
None of which is a substitute for the campaign — they solve different halves. The campaign finds the people who are ready now. The content finds the people who will be ready in the spring, and finds them without paying for each one twice.
Why these three,
and not three you already use.
Because an orchestrator can only drive what it is allowed to drive. A CRM belonging to somebody else can be integrated with, eventually, by a person, after an evaluation and a plan. It cannot be stood up, configured, populated with an owner rule and pointed at a campaign in the eleven minutes that stage four gets.
These three belong to the same company as everything upstream of them. Same account, same wallet, same event vocabulary, same description. That is the entire trick, and it is not a technical one.
You can still use whatever you already have — nothing here is exclusive, and a workflow can push a lead into another system over plain HTTP. But the version that works in an hour is the version where nobody has to ask a vendor for API access first.
What "finding clients" honestly means here.
It means the machinery is running and pointed in the right direction: a campaign going out to an audience, content compounding, a CRM catching everything that comes back, and a dashboard showing what any of it produced. It does not mean customers are guaranteed, and any page that implies otherwise is selling something else.
What it removes is the far more common failure: a product that got built, went quiet, and never found out whether it would have worked — because the launch half was a fortnight of separate setup tasks that nobody had the appetite for after the build.