Pain types at a glance
| Pain type | What usually fails | Primary move |
|---|---|---|
| Marketing without a brief | Vanity spend; “full service” with no KPI | Name channel + KPI → Digital Marketing |
| Referral-only growth | Growth stuck in known circles; no inbound system | Inbound job under Digital Marketing (site may follow) |
| Tools / chat as the brief | WhatsApp ops, prompt threads, no sign-off | Rewrite brief, or one named workflow → AI Integrations |
| Lead sprawl / booking friction | Forms, DMs, calendars with no single path | Production site/app + UI inside that job |
| Multi-step ship | Marketing + site + UI + one workflow, many owners | One agency brief owner across the four services |
Which path for this pain?
Pick one primary service. Discriminator: what job exists when you stop, not “who has AI.”
| Buyer pain / job | Primary path | Why |
|---|---|---|
| Spend starts before a channel and KPI are named; vanity reach is the brief | Digital Marketing | More marketing is not a brief. One channel, one KPI, then spend. |
| Growth is referral-only; you want inbound you can name | Digital Marketing | Referrals vs inbound is a job choice. Inbound needs a named offer + channel, not another reach slide. |
| “We’ll figure it out in chat / the tool”; WhatsApp is the ops system | Rewrite the brief → then AI Integrations & Solutions if the job is one workflow | A chat thread is not included/excluded. Integrations = one named workflow, human-owned brief, not an “AI agency” retitle. |
| “Hire AI” with no workflow named | Neither tools nor a fifth service: name the workflow first | AI may sit inside a perimeter. It is not the product. |
| Multi-step ship across marketing / site / UI / one workflow | AI-native agency habit across the four services | One named brief owner, scope, Final Product: see What an AI-native agency is and AI-native agency vs freelancers and tool stacks. |
| Leads sprawl across WhatsApp, forms, and DMs; no single next step | Websites & Apps Development (+ UI inside) | Booking friction and lead sprawl are production problems: one path to enquiry or booking that ships. |
| Screens and flows sold as a deck that never hands off | UI & UX Design with Websites & Apps | UI sits inside the site/app job, not a separate pitch. |
Fill one row before you buy anyone. Two pains = two jobs = two scopes.
