We don't sell a SaaS. We don't host the runner. We build the automation inside the tools you already use — Slack, Notion, Airtable, Linear, your CRM — and you watch it run on your accounts. If we ever part ways, nothing breaks.
| Spec | Detail | Status |
|---|---|---|
| Code lives in | Your repo · git push, you read diffs | STD |
| Runner on | Your cloud · AWS / GCP / Vercel / etc | STD |
| Connectors | Slack · Notion · Linear · Airtable · CRM | STD |
| Trigger types | Webhook · cron · row-change | STD |
| Migration on exit | None. Code stays where it lives. | STD |
| Build window | 4–6 weeks · first working flow | — |
| Tune retainer | Monthly · optional · cancel any time | STD · cancel any time |
One trigger fans out across the stack. Each box is a tool you already license. No new SaaS. No new login.
You'll see exactly where data lives at each hop, who owns it, and how to reverse it. The map is the contract.
| ID | Node | Scope | Owner |
|---|---|---|---|
| T-01 | Slack | Notify · alert | You |
| T-02 | Notion | Store · log | You |
| T-03 | Airtable | Enrich · upsert | You |
| T-04 | Stripe | Trigger · paid | You |
| T-05 | Linear | Spawn · ticket | You |
| T-06 | Drive | Archive · file | You |
| T-07 | Gmail | Draft · send | You |
| T-08 | Calendar | Invite · book | You |
| Hop | System | Action | Auth | Result |
|---|---|---|---|---|
| 01 | Form.io | Webhook fires | Signed payload | Lead row created |
| 02 | HubSpot CRM | Upsert + score + tag | OAuth · client | Score 78 · hot |
| 03 | Slack | Channel post + DM | Bot token · client | Rep alerted · 2.0s |
| 04 | Google Calendar | Invite drafted, sent | OAuth · client | Booked or pending |
| 05 | Reminder queue | Cron · 24h followup | Internal | Sent · or cancelled |
We hand you the keys. The code runs in your tools, on your accounts, paid for by you. If we walk away tomorrow, your ops keep running.
Most automation studios build it on their hosting and rent it back to you. We don't. The workflow lives in your stack from day one — your runner, your cloud, your repo.
If we ever part ways: nothing breaks. Nothing migrates. No new login. You just stop paying us for monthly tuning.
| § | Clause | Detail |
|---|---|---|
| 04.1 | Code in your repo. Every script, every connector, every secret. We push to a repo you own. You read every diff before merge. | STD git · ssh |
| 04.2 | Runs on your infra. Your cloud, your billing, your auth. We deploy to the account you control. No ASC servers in the loop. | STD aws · gcp |
| 04.3 | Reads your tools. Slack, Notion, Linear, Airtable, your CRM — connected via API keys you issue. Revoke any time. | STD oauth · api |
| 04.4 | No migration. Ever. Built where you already are. No new login. No data export. If we leave, you don't move anything. | STD zero-lift |
Most ops automation breaks slowly — an API deprecates, a field is added, a person leaves. The monthly retainer means we watch the runs, fix the drift, and ship small improvements your team would never get to.
If you'd rather take it from here, that's fine too. The code is yours.
Cancel any time. We hand you the runbook and the keys.
| Date | Tool · change | Impact |
|---|---|---|
| 04.18 | SLACK · pinned new-lead alert + thread routing | +3.4s context |
| 04.15 | AIRTABLE · upsert dedupe on email casing | −12 dupes/wk |
| 04.11 | CALENDAR · timezone fix · EU edge case | 0 misfires |
| 04.07 | STRIPE · refund webhook → Notion archive | +1 route |
| 04.03 | LINEAR · onboard project from new-client form | +1 flow |
Forms come into one tool. Updates go into another. A third needs a manual export. Someone copy-pastes at 7am. We'd map it, draw it, and build it inside the tools they already use.
Target: first working flow in 4–6 weeks. Code lives in their repo. Runs on their cloud. We tune it monthly.
If we ever part ways: nothing migrates, nothing breaks. You stop paying us; the workflow keeps running.