Your team burns
10+ hours a week
on work a script
should do.
I find the manual process eating your team's week and automate it in 1–2 weeks. Fixed price. Working software. No agency bloat.
FOUNDING RATE — FIRST 3 BUILDS, 30% OFF · the honest part ↓
The busywork tax: 4 people × 6 hrs/wk × $55/hr = $68,640YOUR NUMBER NOW a year. Run your own numbers ↓
PROOF
Our inbox runs itself.
The form below, a direct email, a Calendly booking — every inquiry gets parsed, filed into our CRM and pinged to my WhatsApp. 10 seconds, zero humans. The reply is me. Built it in 2 days — watch:
AUTOMATED OURSELVES FIRST — RUNS ON KENTULA.COM
Same machine, your process. The thing your team re-does every week can run itself too — 1–2 weeks, fixed price.
- YOURS COULD BE: INVOICES · CONTRACTS · RATE CONFIRMATIONS · WEEKLY REPORTS
- IF IT REPEATS EVERY WEEK, IT CAN RUN ITSELF
THE HONEST PART — FOUNDING RATE
This studio is new: above you're watching my inbox, not a client's. So the first 3 builds go at 30% off the fixed price — same contract, same 60-day guarantee. In return I ask for one thing: your real before/after numbers, published right here.
Do the math before we ever talk.
Three sliders. Your team, your numbers, your answer.
THE PAYBACK CLOCK
The math I run on every audit call. If your number doesn't beat the build cost, I'll tell you not to automate it.
Where the week actually goes.
Four processes show up in almost every team I audit. Hours are per week, per team.
-
8–12 HRS/WK BACK
Lead & inquiry handling
A lead waits four hours for a reply that should take 40 seconds. After: leads land in your CRM instantly and get a personal answer while they're still warm.
-
5–8 HRS/WK BACK
Document processing
Invoices and contracts arrive by email, and someone retypes them by hand. After: they're read, named, and filed where they belong.
-
3–6 HRS/WK BACK
Self-building reports
Monday morning disappears into five tools and one spreadsheet. After: the dashboard is already built when you open it.
-
6–10 HRS/WK BACK
First-line support drafts
The same ten questions, answered by hand, forever. After: AI drafts the reply from your knowledge base, a human hits approve. Runs on your accounts — nothing feeds third-party models.
Three steps. You're involved for about an hour.
-
01
The Audit — 30 min, free.
You show me the process. I tell you what to automate, what it saves, and exactly what it costs. Fair warning: roughly half my audit calls end with "don't build anything" — the math has to beat the build cost.
-
02
The build — 1–2 weeks.
Built inside the tools you already use — email, spreadsheets, your CRM or TMS. No migrations, no new logins, no six-week discovery phase.
-
03
The handoff — it's yours.
Working software, documented, code in your repo. 30 days of fixes included. And the guarantee: if it doesn't save what the audit promised within 60 days, I refund the build in full.
You talk to the person who builds.
I'm Alex. I take the call, I write the code, I answer when it breaks.
Every number above is a contract clause, not a slogan. NDA signed gladly · credentials returned at handoff · your repo from day 1 · on the call I'll walk you through my own automations, running live — the real thing, not screenshots.
Straight answers.
What does an automation project cost?+
Fixed price, quoted on the audit call — most projects land in the $2,000–5,000 range. The benchmark is your own math: if the process burns ~$1,000/month in team time, the build pays for itself in a quarter. If it doesn't, I'll tell you it's not worth automating.
Do we need to switch tools or platforms?+
No. I integrate with what you already use — your CRM, your inbox, your spreadsheets. Migration projects are a different, much sadder conversation.
What about our data — do you need access?+
Only after we sign, and only to the systems involved. Happy to sign your NDA first. Credentials are used for the build and handed over / revoked at handoff.
What if it breaks?+
30 days of fixes are included in every project. After that you can take full ownership with the documentation — or keep me on a small monthly retainer for monitoring and tweaks. Both are fine.
What does the 60-day guarantee actually cover?+
The audit ends with a written number — the hours this build must save you every week. We measure your baseline before I write any code, and if the automation doesn't hit the promised number within 60 days of launch, I refund the build in full. Measurement included — it's a contract clause, not a slogan.
What if you get hit by a bus?+
Everything lives in your repo from day one — documented, with a handoff walkthrough. Any competent developer can pick it up. And the 30 days of fixes are in the contract, not a promise.
Am I locked into a retainer?+
No. Fire me the day after launch — the code, the docs, and the credentials are yours. Want monitoring and small tweaks after? That's an optional retainer, $150–300/mo — an offer, not a lock-in.
Does our data end up in someone else's AI?+
No. Drafts and processing run inside your accounts and your stack. Nothing you own is used to train third-party models. Happy to put it in the NDA.
Get your hours back.
Free 30 minutes. What to automate, what it saves, what it costs — you keep the plan either way.
Or old-school — hello@kentula.com · Book directly: calendly.com/kentula/audit
Protected by Cloudflare Turnstile · Privacy Addendum