Get a free build plan
How we build

The back end, in the open.

The process from your first answers to day 30, the real n8n canvases we run, the demo, the sample plan, and why the work is set up this way.

0systems built for our own operation first: list engine, inbox triage, reply engine, campaign builder
0leads listed with one-line openers in one afternoon, for our own outreach
0email addresses verified before a single message goes out
0 daysfrom your answers to a written build plan. No calls required.
We use our own systems first. Every number on this page is from our own operation, measured in August 2026. Client results are published only with written permission.
Our logs · Aug 2026
list engine · recruiting · 100 leads → 96 with email → 100 openers · 1 min 51 slist engine · agencies · 100 leads → 100 with email · batch oklist engine · insurance · 100 leads → 92 with email · batch okverification · 195 leads checked before any send → 177 verified · 18 rejected · okinbox triage · inquiry classified · threaded reply from Rotewise Team · same minuteinbox triage · newsletter · classified DISQUALIFIED · no reply · okreply engine · pricing question · not in knowledge base → flagged to human · digest sent · okmailboxes · 9 sending mailboxes warming · 20/day · 8-minute gaps · day 1campaign builder · 6 campaigns created · A/B copy · Mon–Sat 07–19 ET · draftlist engine · recruiting · 100 leads → 96 with email → 100 openers · 1 min 51 slist engine · agencies · 100 leads → 100 with email · batch oklist engine · insurance · 100 leads → 92 with email · batch okverification · 195 leads checked before any send → 177 verified · 18 rejected · okinbox triage · inquiry classified · threaded reply from Rotewise Team · same minuteinbox triage · newsletter · classified DISQUALIFIED · no reply · okreply engine · pricing question · not in knowledge base → flagged to human · digest sent · okmailboxes · 9 sending mailboxes warming · 20/day · 8-minute gaps · day 1campaign builder · 6 campaigns created · A/B copy · Mon–Sat 07–19 ET · draft
Built on n8nGoogle WorkspaceOpenAIApifyFirecrawlInstantly
How it works

No discovery calls unless you want one.

Everything in writing, read when you have time.

Day 0

You describe the process

Six short questions on the site (or one email): what you do, the process that eats the most time, the tools you already use.

Day 2

Written build plan

What we'd build, what we need from you, the date it ships, and the price if you keep it. Read it when you have time.

Day 7

Working version on sample data

You watch it run before it touches your accounts. We adjust until it fits the way you actually work.

Day 30

Keep it or don't

If it earned its place, we agree the flat price, the workflow moves into your n8n and we keep improving it. If not, you keep what it produced and owe nothing.

Watch it work

Three emails arrive. Here is what the system does with each.

The inbox triage and reply engine on three sample emails. Real rules: qualified inquiries get a threaded reply, noise gets nothing, price or integration questions go to a person.

hello@rotewise.com · inbox
Jordan Reyes 09:41
Automating candidate intake for our staffing firm
Weekly SaaS Digest 09:43
10 growth hacks you can't miss this week 🚀
Morgan Lee 09:47
Re: question about pricing and our HubSpot setup
waiting for mail…
Build log

Real canvases, real runs. This is what you get.

The actual n8n canvases we run, with measurements from our own logs.

n8n canvas of the Rotewise list engine: Apify Leads Finder to Google Sheets to OpenAI openers
list engine · live

Lead list with one-line openers

Pulls decision makers that match a niche, drops duplicates and anyone we have contacted before, keeps only rows with an email, and writes a short opener from each person's own profile into a sheet.

  • Leads per run100
  • Rows with a usable email96 of 100
  • Openers written per batch100 in 1 min 51 s
  • Tool cost per 100 leadsunder $0.50
n8n canvas of the Rotewise inbox triage: Gmail trigger to OpenAI classify to IF to reply
inbound triage · live on our own inbox

Inbox triage and drafted replies

Every new email is read, classified, and either answered with a threaded reply that asks the three discovery questions, or left alone. Spam and newsletters get nothing. Our own inquiries run through it today.

  • Checks the inbox every60 seconds
  • Reply lands in the threadunder a minute later
  • Questions about price or integrationsflagged to a human
  • Fabricated claims in repliesblocked by rule
Why Rotewise

Four things we do differently.

01.

Built first, paid after

You see a working version on sample data before any money changes hands. The risk sits with us.

02.

Fixed price, in writing

One flat number agreed before anything is switched on. No hourly meter, no surprise invoices.

03.

You own the system

Once you keep it, the n8n workflow, sheets and prompts are yours. Leave any time after that and everything keeps running without us.

04.

Everything in writing

No discovery calls unless you want one. Plans, questions and progress arrive as email you can read on your own schedule.

What we build, by niche

Fixed-scope systems. Each one starts free and becomes yours the day you keep it.

01.

Recruiting and staffing agencies

  • Client list of 500 hiring managers with openers, in 5 days
  • Applicant inbox assistant: tag, draft, log, in 7 days
02.

B2B marketing and SEO agencies

  • Proposal template that fills itself, first draft in 48 hours
  • 300 look-alike companies from your best client, in 3 days
03.

Independent P&C insurance agencies

  • Renewal follow-ups at 60, 30 and 7 days, running in 7 days
  • Quote requests answered within 5 minutes, tracked in one sheet
What you get on day 2

A sample build plan, so there are no surprises.

The document you get two business days after your answers. This example is for a hypothetical 12-person staffing firm asking for an applicant inbox assistant.

build-plan · applicant-inbox-assistant · sample.pdf
Prepared for [a 12-person staffing firm]Illustrative · figures are examplesDay 2 after your email

The problem you described

Around 200 applications a week arrive by email. Two recruiters spend roughly six hours a week opening, reading and forwarding them, and good candidates go cold while they wait.

What we will build

An n8n workflow, run from our n8n during the free period and moved into yours when you keep it, that reads each new application, tags it (fit, not a fit, question), drafts a reply in your wording, logs every message to a sheet, and files the email under the right label. Nothing is sent without a person's click until you decide otherwise.

What we need from you

A Google sign-in for the shared inbox (or a forwarding address), three of your own past replies so the drafts sound like you, and the list of roles you are currently filling.

Dates

Working version on sample data: 7 days from your sign-in. Live on your inbox: the day you approve the sample run. Free period: 30 days from go-live.

If you keep it

Build: $1,500 one-off, including 90 days of adjustments. Build + Run: $1,950, with six months of monitoring, prompt tuning and one change request a month. Both fixed in this plan. The workflow, prompts and runbook are handed over on payment.

What we will not do

Send anything to a candidate automatically until you switch that on. Store applications anywhere outside your own Workspace. Leave anything running in your accounts if you decide not to keep it. Claim results we have not measured.

How we measure it

Hours per week spent on intake before and after (you tell us), share of applications answered within one business day, and drafts you sent without editing. You get the numbers in a sheet, not a slide deck.

Operated through Claude

Our own back office runs as an AI connector.

We run Rotewise on its own medicine. The intake list, the lead engines, the payment log and the health of this very website are wired into Claude over MCP, the open protocol for connecting AI to software, as a private connector. The AI reads the numbers and runs the checks; a person gates anything that leaves the building. It is how a small operation behaves like a staffed one.

What that means for your build

Every system we hand over is built from the same blocks we operate this way: webhooks in, sheets and mail out, one log per run. Nothing exotic, nothing locked in. If you want your system reachable from your own Claude, the same plumbing does it, scoped to your data only.

Ask for it in your free build plan and we will put it in writing.
Already a client? How your access works
Start here

Tell us the one process that costs you the most hours.

Six short questions on the home page. Within two business days you get what we would build, when it ships and what it costs if you keep it.

Get a free build plan