Stage four
Di half wey customers dey come from
Almost everything inside dis category go stop for "built" and go call am finish. Product wey don build but nobody dey look am na just hobby wey get domain name. So di pipeline dey continue: CRM wey dey wait for di first conversation, campaign wey go go out, and blog plus social presence wey go start to fill up dat same afternoon.
Dis stage dey use three more members of di family — iKonekt, clickSomo and FABLS — and e dey use di same written description wey everything else build from. Na why di campaign first line go talk wetin di site headline talk, and di blog plan go argue di case wey di document argue.
Di order matter. Di CRM suppose go up before di campaign, because campaign wey dey generate replies enter inbox wey nobody dey watch worse pass no campaign at all: e go burn di one first impression wey you get, and e go produce folder of people wey write to you and nobody answer dem.
Fost
iKonekt: place wey demand fit land, with name attach to am
Every channel wey customer fit use go land inside one inbox, as contact wey get recorded source, owner, and thread wey start from di first word wey dem talk. Chat, live chat, forms, di reach-me button, call-me requests, e-mail, phone, QR codes ontop anything wey dem print.
Ownership from di moment e land
Every lead na somebody work from di second e land, no be from di time somebody notice am. Di difference between dose two times na where new products dey lose dia first ten customers.
Source dem keep am, permanent
E reach di individual flyer or link, no be just "offline". Three months later, "di campaign work?" go get answer wey get number inside, no be three opinions.
Reach di invoice
Di pipeline dey run from first contact reach paid invoice, KSeF join, so di first sale no go need spreadsheet and somebody accountant wey dey improvise.
Launch no be announcement. Na di first customer.
clickSomo: di kickstart campaign
New product problem no be conversion, na say nobody know say e dey exist. clickSomo go run di first push across di channels wey people dey actually read: e-mail, SMS, push notifications, and — for di kind business wey e still dey work pass anything digital — printed letters.
Dem dey run am as funnels no be blasts, so di second message depend on wetin di first one do. If dem open am but no click, e go get different follow-up from di one wey dem no open at all, and anybody wey reply go comot from di sequence completely, because dem don turn to conversation inside di CRM, no be name for list again.
Written once, again: di campaign copy dey generated from di same description as di site. Nobody need re-explain di product to di mailer, and no version of di pitch dey wey only dey exist inside e-mail wey somebody write for eleven for night.
- 1Day 0 — e-mailDi case, inside six sentences, with di price inside. Short links, redirects wey dem count, no tracker anywhere.
- 2Day 2 — branchDem open am, no click → another angle. Dem no open am at all → different subject line, send am for different hour.
- 3Day 3 — SMSOne message, to di segment wey engage. Quiet hours dey respected without anybody go configure dem.
- 4Any replyE go comot from di sequence, e go turn to thread inside iKonekt with owner ontop am.
- ·Wetin e no dey doBuy list. Di audience na your own; na di sequence dem dey automate.
E-mail · SMS · push · postTriggers, no be blasts
- 1PlanThree-to-six month editorial plan, wey dem build from di written case and di words wey di product buyers dey actually search for.
- 2Writer demPosts wey dem draft and publish ontop schedule, inside di brand voice, with pictures wey carry dia licence.
- 3SocialsDi same plan wey dem push go di accounts, at di rhythm wey each one like.
- 4Reports demEvery week and every month, e go talk wetin comot and wetin e do. You go read am in four minutes, no need twenty minutes to decode am.
- ·Why now, no be laterContent na di only channel wey im reward dey come late. If you start am for month four, di reward go land for month ten.
Months, no be just intentionSame voice as di site
FABLS: blitzscaling di visibility half
Blogging and social presence na di slowest-paying channels wey new product get, and na exactly why dem dey postpone dem, and exactly why postponing dem dey cost money. Di compounding no go start until di first post dey exist.
FABLS dey run both automatically: one plan wey dem measure in months, writers wey dey produce di posts, di social accounts wey dey feed from di same plan, and one report every week and month wey go talk plainly wetin happen. E start di same afternoon as everything else, so month four go inherit three months of work instead of one resolution.
None of dis one na substitute for di campaign — dem solve different halves. Di campaign go find di people wey ready now. Di content go find di people wey go ready for spring, and e go find dem without paying for each one two times.
Why dis three, and no be three wey you already dey use
Because one orchestrator fit only drive wetin dem allow am to drive. One CRM wey belong to another person, person fit integrate with am later, after evaluation and plan. You no fit stand am up, configure am, put owner rule inside and point am at one campaign in di eleven minutes wey stage four get.
Dis three belong to di same company as everything wey dey before dem. Same account, same wallet, same event vocabulary, same description. Na di whole trick be dis, and e no be technical one.
You fit still use wetin you already get — nothing here na exclusive, and one workflow fit push one lead enter another system over plain HTTP. But di version wey work in one hour na di version wey nobody need ask vendor for API access first.
Wetin "finding clients" really mean here
E mean say di machinery dey run and e dey point di right direction: one campaign wey dey go out to one audience, content wey dey compound, one CRM wey dey catch everything wey come back, and one dashboard wey dey show wetin any of dem produce. E no mean say customers dey guaranteed, and any page wey imply otherwise dey sell something else.
Wetin e remove na di more common failure: one product wey dem build, e go quiet, and e never find out whether e for work — because di launch half na two weeks of separate setup tasks wey nobody get appetite for after di build.