CATEGORY 01
Customer-facing
Onboarding sequences, NPS / feedback loops, support-ticket routing and triage, lifecycle emails, churn-signal alerts, expansion-trigger detection.
Service · Business Process Automation
Automate the work that isn't outbound.
n8n, Make, Zapier, and AI agents wired into your real systems. Customer onboarding, RevOps hygiene, support routing, internal approvals, or whatever's quietly eating your team's week. Tech stack, you own it. We charge only on performance.
- 14-day build window
- Flat fee, no hourly billing
- Written runbook on every workflow
We already ship production automations every day, Clay workflows, reply parsers, CRM sync, AI personalization at scale. The same engineering applies to your ops.
Flat fee
priced per workflow, not per hour
At cost
all tooling billed to you directly, no markup
You own it
workflows ship with a written runbook, not a black box
↳ What we automate
Four categories.
Hundreds of workflows.
If a workflow is repetitive, has a clear trigger, and a defined end state, we can probably automate it. If it isn't, we'll tell you on the call.
CATEGORY 02
Revenue operations
CRM hygiene, lead routing and round-robin, quote and contract workflows, deal-stage automation, pipeline reporting digests, attribution stitching across tools.
CATEGORY 03
Internal operations
Employee onboarding and offboarding, approval chains, document parsing, invoice and PO processing, recurring reporting, cross-platform data sync, scheduled digests to Slack or email.
CATEGORY 04
AI agents
Inbox triage and draft replies, meeting-prep briefs, research agents on named accounts, internal Q&A on your company docs, support deflection bots, content moderation pipelines.
↳ Concrete examples
Workflows we've shipped
that pay for themselves.
These aren't hypotheticals. Each one is patterned after a real engagement, with the before/after time savings the client actually saw.
01
Inbound demo request → enriched → routed → calendar invite
Before: 18 minutes of manual work per request (enrichment, Slack ping, CRM update, calendar pull). After: 90 seconds, fully automated, AE gets a brief in Slack before the call. Stack: n8n + Clay + HubSpot + Slack + Cal.com.
02
Support ticket auto-triage with AI classification
Before: 2 hours/day for the support lead just sorting and routing. After: Tickets land in the right queue with a suggested draft reply and severity score. Lead reviews and ships. Stack: n8n + Anthropic + Intercom + Linear.
03
Employee onboarding from offer accepted → day one ready
Before: 6+ tickets across IT, HR, and ops for every new hire, often missed. After: A single trigger provisions accounts, sends welcome emails, schedules onboarding meetings, and posts a Slack intro thread. Stack: Make + Google Workspace + Notion + Slack + 1Password.
04
Weekly RevOps digest with deal-risk flags
Before: Head of Sales spending Sunday night building a slide. After: A digest hits the leadership channel every Monday at 7am with pipeline movement, at-risk deals, and the three calls that need a manager nudge. Stack: n8n + HubSpot + Gong + OpenAI + Slack.
↳ The stack
We pick the right tool
for the job.
No religious wars. n8n for serious workflows. Make and Zapier when speed-to-ship matters. Custom code when the platform tax exceeds the value. We tell you which on the scoping call.
n8n
Self-hosted or cloud, our default for production workflows with complex logic
Make
Visual flows with deep app coverage when scenarios are well-supported
Zapier
Speed-to-ship for one-off integrations and lightweight glue
Airtable · Supabase
Data layer behind workflows, dashboards, and internal tools
OpenAI · Anthropic
LLMs for classification, drafting, summarization, and agentic flows
Slack · Microsoft Teams
Notifications, approvals, and conversational interfaces for internal tools
Google Workspace · Microsoft 365
Email, calendar, docs, and drive as both triggers and destinations
HubSpot · Salesforce · Pipedrive · Attio · Notion
CRM and knowledge-base sync, with bi-directional update logic
↳ How we work
From discovery
to live in four weeks.
Tightly scoped phases. You know what's happening every week. We don't disappear into a Notion doc for a month.
Week 1
Discovery & map
Days 1 – 7
- ✓ Workshop with the people doing the work
- ✓ Map the current process end-to-end
- ✓ Identify the highest-leverage workflows
- ✓ Scope, price, and stack decisions in writing
Weeks 2–3
Build & test
Days 8 – 21
- ✓ Build in a staging environment
- ✓ Test with real data and real edge cases
- ✓ Internal review and walkthrough with you
- ✓ Refine prompts, retries, and failure modes
Week 4
Deploy & document
Days 22 – 28
- ✓ Deploy to production with monitoring
- ✓ Notion runbook for every workflow
- ✓ Team training and handoff
- ✓ Optional ongoing ops retainer
↳ Pricing posture
Flat fee per workflow.
No hourly billing. No labor markup.
We scope each workflow up front, quote a flat build fee in writing, and hold to it. If a build takes longer than we expected, that's our problem. If it takes shorter, that's our edge. Either way, the number on your invoice matches the number you signed.
All third-party tooling, n8n hosting, Make scenarios, Zapier seats, OpenAI tokens, Supabase databases, is billed to your accounts directly. We don't touch it, mark it up, or hide it inside a "platform fee."
Typical engagements: $3K–$25K per workflow build depending on integration count and logic complexity. Multi-workflow packages and ongoing ops retainers quoted on the scoping call.
Book a scoping call↳ Fit check
Is Business Automation
right for you?
Good fit
You should book a call
- ✓ Specific workflow that hurts every week
- ✓ Engineering team is busy / unavailable
- ✓ You've outgrown a single-tool Zapier setup
- ✓ You want to ship LLM agents into your ops
- ✓ Comfortable owning the system after handoff
Maybe
Talk to us first
- ? Highly regulated data (HIPAA, SOC2 scope)
- ? Legacy systems with no API
- ? "We need an internal tool", depends on shape
- ? Single one-off integration under $2K of scope
- ? You already have a workflow you want us to take over
Not a fit
We'll say no
- ✗ "Build me an entire SaaS product"
- ✗ Process isn't actually defined yet
- ✗ You want hourly billing for staff aug
- ✗ No budget for the underlying tooling
- ✗ Want secrecy / black-box (we ship the source)
↳ Common questions
Everything you should know
before we talk.
You do. From day one. Every workflow ships in an instance owned by your team, your n8n, your Make org, your Zapier workspace, your Supabase project. We're never the single point of failure between you and your ops.
For long-horizon workflows we default to self-hosted n8n on infrastructure you own (Hetzner, Railway, or your existing cloud), which neutralizes vendor risk. For higher-velocity workflows we use Make or Zapier and accept the platform lock-in tradeoff. We discuss the tradeoff explicitly during scoping so you're choosing it with eyes open.
Three options. (1) Your team, every workflow ships with a Notion runbook and a 2-week support window. (2) We retain the maintenance via a defined monthly ops retainer. (3) Mix, we run it for the first 90 days, your team takes over once the system has stabilized and the runbook is battle-tested.
One-offs are the default. Retainers are opt-in. We quote per-workflow and you decide whether you want a single build, a multi-workflow package, or ongoing ops after launch.
Two differences. First, we operate production automations at GTM scale every day, the failure modes, retries, monitoring, and idempotency patterns are second nature. Second, we ship a Notion runbook, error monitoring, and a written handoff. A typical freelancer ships a Zap and an invoice.
Yes, most of the workflows we ship now have at least one LLM step. Classification, drafting, extraction, and summarization are the cheapest wins. We pick the right model per step (Claude, GPT-4-class, or open-source via API), version the prompts in your repo or Notion, and monitor token spend.
Yes, see GTM Automation. Many clients buy both: GTM Automation on a pay-per-meeting basis to drive pipeline, and Business Automation to clean up the ops debt that the new pipeline volume exposes.
↳ Last step
Pick a time that
works for you.
30 minutes. Bring the workflow that hurts the most. We'll tell you if we can automate it, what it would cost, and which stack we'd reach for, on the call, not three days later.
- 30 minutes, on a calendar slot you pick below
- Honest scope and stack recommendation
- Flat-fee quote in writing before any work starts