automation 03
Offer & Lead Gen Engine
Ten workflows on a Postgres backbone. Scores an offer against the value equation, rebuilds the weakest lever, designs one lead magnet per persona per awareness stage, refuses to launch it until the nurture pipeline exists, enforces one channel at a time, and tracks daily activity against a committed number.
- Install
- Install from $3K
- Timeline
- About a week to install and seed the first offer
- Runs on
- Your own n8n
- 01
88
nodes
- 02
10
workflows
- 03
13
tables
- 04
24
SQL statements
Most sales problems are offer problems wearing a disguise, and most traffic problems are capture problems. Fixing either one downstream is expensive.
how it runs
the workflows
- 0
Orchestrator
Offer intake form, daily tick and the daily brief.
- 1
Offer audit
Value-equation scoring, one to ten on each lever, with the weakest lever named rather than left to interpretation.
- 2
Value rebuild
Lever-specific rebuild actions. Anything that proposes a discount is discarded, because a price cut is not a value improvement.
- 3
Magnet design
Archetype and format selection, a spec sheet, and the nurture checklist seeded. Refuses a second magnet for a persona at a stage that already has one.
- 4
Nurture gate
Blocks promotion until welcome, nurture, next-step and exit assets all exist and are marked ready.
- 5
Channel plan
Channel sequencing gate and the daily activity commitment. Refuses a second channel until the first is dominated, and refuses paid on an offer with unknown unit economics.
- 6
Daily activity
Activity webhook and a nightly shortfall alert against the committed number.
- 7
Amplifier activation
Customers, then employees, then affiliates, then agencies, in that order. Refuses affiliates without a channel at 3:1 LTV to CAC, and refuses agencies for a channel you have not run yourself.
- 8
Reporting
Weekly economics, kill-criteria breaches and dominance promotion.
- E
Error handler
Failure logging and alerts.
how it holds up
01
The gates are the product
Five of the ten workflows exist to say no. Disable them and you have a CRM with extra steps. Every refusal arrives by email naming the specific rule and the specific fix, so a no is always actionable.
02
Claude scores, the database decides
The model proposes lever scores and magnet specs. The weakest lever is then recomputed from those scores in code rather than trusted, extra capture fields are dropped, price actions are screened out, and every gate is a SQL condition. The model has judgment; it does not have authority.
03
It governs the top of the funnel only
Nothing here sends anything to a prospect. What you offer, what you give away, which channel you commit to and who amplifies it. Delivery is a different system.
what it will not do
It will tell you no, often, early, and in writing. That is the value, and it is also why it is a poor fit for anyone looking for a tool that agrees with them.
It needs real unit economics to gate on. If you do not know your LTV or CAC, the first output is a list of what to go and measure.
It governs strategy, not delivery. Pair it with the Lead Generation Engine if you need the sending half.
you supply
- n8n, cloud or self-hosted
- Postgres, Supabase is the least friction
- Anthropic API key
- An email address the gates can write to
running cost
Low. The expensive calls are the audit and the magnet design, and both run on a change rather than on a timer.
Billed by your own providers, not by us. There is no platform fee and no seat count.
InstallOffer?
Install from $3K, about a week to install and seed the first offer. Tell us about your setup and we will confirm it fits before taking anything.