About · founder, posture, positioning

A boutique automation studio —
built by a service-business operator, for them.

One page, three pillars: who is behind the desk and why, how we hold the EU AI Act / FTC line without overpromising, and where Routelet sits between a coach, a course, and an agency bench. No fluff, no manifesto, no upsell — the story, the posture, the contrast, side by side.

Read the founder noteSee what we ship
Reply in
≤ 1 business day
Audit
$0 · 30 min
Quote
fixed scope
Founder note · how this studio started

One operator. One n8n runtime. One weekly Loom.

The story is short on purpose. We picked one operator who scopes and ships, we run every build on a single n8n runtime, and we meet every week on a Loom — not a status meeting, an asynchronous written debrief. The notes below explain why.

Founder note
Why one operator, not an agency bench.

I started Routelet after building thirty-plus automations for my own service-business customers — solo dental practices, indie real-estate teams, two-person HVAC shops, an optometry back office. Every one of them had the same leak: a human pasting data between five tools at 11pm because nobody owned the seam.

The leaks did not show up in a pitch deck. They showed up in a half-finished CRM nobody trusted, an inbox full of replies nobody had time to write, and a Monday morning standup where the same Friday question was still the bottleneck. I shipped each one end-to-end on a single n8n runtime, and the operators kept the build — not my agency, them.

That is the studio you are looking at. One operator who scopes the workflow on the audit screen-share, ships the build on the same n8n runtime, and meets the team on the post-launch Loom. No rotating bench, no "your project manager will reach out" handoff in week three, no hourly upsell.

We pick one operator, run the audit, ship the build, and stay on-call during the cover window. When the cover window ends, the asset — code, runbook, Loom — is yours, and the credentials are yours to revoke. That is the only way we know how to keep the work honest.

  1. 2023

    Shipped 30+ automations for service-business customers running n8n at small scale — solo dental, indie real-estate, two-person HVAC, optometry back office.

  2. 2024

    Spun the side builds into a single fixed-scope process — free audit on a Monday, fixed-scope contract by Friday, Loom handover on the last day.

  3. 2025

    Folded EU AI Act / FTC posture into the audit memo: data provenance, human-oversight gating, and the ledgers we keep on record for the regulator.

  4. 2026

    Routelet ships one workflow at a time, on one n8n runtime, by one named operator. No agency bench, no rotating team, no hourly billing.

Compliance · EU AI Act / FTC posture

What we put in writing. What we will not promise.

Compliance-aware is part of the studio's posture — not a bolt-on. The audit memo carries the disclosure front of mind, the build carries it into the runtime, and the ledgers we keep on the record are the ones a regulator (or an FTC notice-letter writer) can actually audit. Two columns, side by side.

What we WILL put in writing
Items the contract and the audit memo defend, in plain terms.
  • Audit memo in writing before any contract is signed.
  • Fixed scope, fixed price, locked on the same call as the audit memo.
  • Data provenance legible in the n8n workflow — inputs, outputs, and the seam that stores them.
  • A post-launch cover window (14, 30, or 90 days, sized to the tier) before the handover closes.
  • EU AI Act Art. 14 human-oversight obligation on customer-facing outputs — escalate, do not decide.
What we WON'T promise
Things we explicitly do not market, even when buyers ask. The audit memo is the deliverable; the contract is the boundary.
  • No AI accuracy guarantee, no "hallucination-free" claim, no SLA on output sanity beyond the cover window.
  • No "compliance-as-a-service" — we scope, document, and audit; you own the regulatory posture on your side of the seam.
  • No certification, license, or auditor credentials we do not actually hold (we name only what the audit memo can defend).
  • No claim a workflow is "EU AI Act compliant in the abstract" — only that it conforms to the audit memo's documented controls on your content.
Positioning · boutique vs coach

What we are. What we are not.

The contrast is on the home page and the pricing already — but the buyer always asks "are you a coach too?". Routelet is an automation studio: we scope the workflow, ship the build on one n8n runtime, and stay on-call during the cover window. We do not run courses, sell masterminds, or bill hourly.

Boutique · builds the workflow
What you get from a Routelet build, in the language the audit memo uses.
  • The audit

    A 30-minute screen-share with the named operator and a fixed-scope quote on the same call.

  • Workflow shipping

    One n8n workflow, scoped, audited, and shipped under a single fixed-scope contract in 1–6 weeks.

  • After-delivery care

    14 / 30 / 90-day cover window sized to the tier, plus a retainer option for incident-grade breakage.

  • Value transfer

    Code, runbook, Loom handover, and the credentials — yours from week one, revocable any time.

Coach or course · sells the playbook
What we explicitly do not do — even when it is what the buyer thinks they want.
  • The audit

    A free PDF, a 7-day email course, and a discovery call that books the next call.

  • Workflow shipping

    A Loom template, a Notion workspace, and a "build it yourself with our prompts" kit.

  • After-delivery care

    A private Discord channel and an asynchronous weekly Loom you can re-watch, not reply to.

  • Value transfer

    A vocabulary, a framework, and a community; the outcome depends on what the buyer does with it.

Routelet does not run courses, sell masterminds, or bill hourly. The audit is the audit; the tier your scope matches just tells us what to put in the contract.

EU AI Act / FTC · quick answers

The four compliance questions buyers raise most.

Each answer below is one to two sentences, drawn from the same posture the audit memo cites. The six-question version of this list lives on the FAQ page; these four are the ones the compliance conversation lands on.

  • Why no AI accuracy guarantee?

    Because no AI tool ships one. The audit memo documents the human-oversight gate on every customer-facing output — anything above the approval threshold escalates to a human with one-click context. The contract covers the cover window, not a hallucination-free SLA.

  • Why no "compliance-as-a-service"?

    Because we scope, document, and audit — we do not stand between you and the regulator on your side of the seam. Compliance posture is part of the build, not a subscription. The audit memo names the controls on your content; you own the regulatory posture from there.

  • Does the audit memo hash?

    Yes. Every memo names the inputs, the workflow, the data-provenance ledger, the human-oversight gates, and the cover window — so it can be re-walked at any time by you, your team, or a regulator. We do not black-box the build.

  • What about post-launch?

    A 14 / 30 / 90-day post-launch cover window is sized to the tier and written into the contract. After the window closes, a flat-capacity retainer is the option for teams that want the same operator on incident-grade breakage each month.

Ready to ship? Send the brief.

Book the free audit. Then we will tell you whether.

Four fields, one 30-minute screen-share, and a two-page memo you can act on whether or not you hire us after. Reply within one business day — or pick a slot directly and skip the wait.

Book a free auditSend your scope instead

Fixed scope, signed in writing. One operator, one n8n runtime, one weekly Loom.

One operator, one page, one fixed-scope contract. The audit is the deliverable — the tier your scope matches just tells us what to put in the contract. Prefer email? touchflow@polsia.app

— Routelet · TouchFlow