01
One interview
Three hours with me, once. You explain how the business really runs and what should leave your plate first.
How it works
I install the system once. Then it runs every week.
This page is the mechanism. A 3-hour operator interview, an install across days 1-7, your first approval loop by day 14, and a weekly rhythm after that. You message me in the channel you already use; you never learn a portal.
3 hrs
operator interview
day 7
install complete
day 14
first approval loop
$15K setup + $4K/mo. $39K first six-month commitment, 14-day fit window.
the mechanism · one request, tracedapproval-gated
you · whatsappchase the renewal, send the invoices
RRoki + AI team
Gmail
LinkedIn
Stripe
work done and logged in your tools
2 approvals, back in your chat
Day 0 · the operator interview
Three hours of questions, before any software. The install is only as good as the map.
We sit down once, on a call. I ask how sales actually closes, who chases invoices, what support promises, which words you would never use, and which decisions must stay yours. By the end, the lanes are named - and so is the one person on your side who approves.
This is the same interview I schedule on the fit call. It is the only meeting the setup asks of you.
day 0 · the operator interviewapproval-gated
Days 1-7 · the install
I connect the real tools and build your private brain.
Gmail, LinkedIn, WhatsApp, calendar, CRM, billing - connected to a private Dewx workspace, reads open first, writes gated from day one. Then your offers, threads, writing samples, and policies become a working memory that only your account uses.
You lend access; you do not operate software. Where local account context matters, a dedicated Mac running DewLink keeps sessions and data close.
days 1-7 · the installapproval-gated
Gmail
Calendar
LinkedIn
WhatsApp
CRM
Your private installDewx web · DewLink · local
By day 14 · the first approval loop
The first drafts reach you through one gate.
The AI team prepares real work from your real context. I check tone and judgment before anything reaches you. Then you see a short queue: approve, edit, or reject. Nothing leaves the system without passing that gate - outbound, invoices, and public content stay gated by default.
Olive means handled. Amber means held for your decision. Every action keeps its trail: the context used, the draft, the approval, the send state, the owner.
by day 14 · the first approval loopapproval-gated
Renewal reply
Invoice batch
Outreach drafts
Support reply
Renewal reply sent · logged
Support reply sent · logged
Invoice batch · waiting on you
Outreach drafts · waiting on you
Every week after · the rhythm
The loop runs weekly. You keep the decisions.
Monday opens with a brief. Through the week, work is handled in your tools and exceptions come to you as approvals. Friday closes with the report: what moved, what is stuck, what needs you. Every correction you make becomes a rule the system keeps.
The numbers in the diagram are an example week - the real ones arrive each Friday.
every week after · the rhythmapproval-gated
What I need from you
Enough truth to run it right.
The setup is not heavy, but it needs honesty. If I understand how you actually sell, support, invoice, and decide, I can remove the work without removing your judgment.
02
Account access
Read access and approved connections for the tools we operate. Sensitive writes stay gated behind your approval.
03
Writing and policy samples
Recent outbound, support replies, pricing language, refund rules, and examples of what sounds like you.
04
One approval owner
A single person who can say yes, no, or edit. The cleaner this is, the faster the loop stabilizes.
The honest capability line
You buy the operating relationship, not unfinished magic.
Some pieces are live, some are being hardened, some are roadmap. The promise you buy today: I run the work, and approvals stay in your hands.
Live
The operating layer I work in daily
The Mac workspace, local database, inbox, CRM, calendar, and the approval queue. DewLink already gives your account a local tool layer the system runs through.
Building
Tighter web-local mirroring
The web workspace and the Mac layer are being hardened so inbox state, CRM, and send states stay mirrored cleanly between them.
Roadmap
Local AI, voice, overnight prep
Designed and documented, not sold as finished behavior. What you buy today is operated work with approval rails - and that part runs now.
The next step
If this sounds like your company, it starts with a 30-minute fit call.
If it's a yes, kickoff is within two weeks: the 3-hour operator interview, the install across days 1-7, and your first approval loop by day 14.
30 minutes, with me, no pitch deck. If it's not a fit, I'll tell you on the call.