Price
Pricing
Custom scope
Priced after a short qualification.
How it starts
- Book a demo call
- We check the fit against your audience and setup
- You get a scope and price before any build
Email outreach infrastructure
Outreach that reads like it was written for one person
A model writes each email from what your database knows about the contact, and sends it from domains and accounts you own.
Built to move
- Research and drafting time (target: lower)
- Follow-up consistency (target: higher)
- Qualified conversations (target: higher)
- Personalized from your dataEvery sentence ties back to a field in the database.
- Owned infrastructureIt runs on your domains, accounts and cloud, not a shared outreach tool.
- Checked before it sendsRules catch banned phrases and wrong lengths. A person reviews.
Every sentence comes from a field in your data
The database sets what we know about each person. A model writes the email from it, and your own domains send it.
The database row
- 1RoleHead of partnerships
- 2SpecialtyPayments infrastructure
- 3Size tierSmall (11 to 50)
- 4Peer proofExample Peer Ltd, confirmed
- 5Buying roleDecision-maker
When a field is unknown, the email leaves it out instead of guessing.
The email it becomes
Hi Alex,
Most heads of partnerships1 in payments infrastructure2 still handle this by hand. Example Peer Ltd4 has already moved.
For a team your size3, it is worth doing once, properly. Worth a quick call this week5 to see if it is relevant for Example Ltd?
- WrittenOne model call per contact
- CheckedLength, banned phrases, required details
- ReviewedA person approves before it sends
- SentFrom domains you own, paced by warm-up
- FollowedA reply stops the sequence
Works with
- Gmail on Google Workspace
- Your CRM
The build, at a glance
Built on the data foundation, run on infrastructure you own.
Inputs
- Your databaseFields from the data foundation
- Your offer and voiceWhat you say, and how
- Your exclusionsSuppression and do-not-contact lists
Engine
- One model call per contactWritten from that contact's fields
- Quality rulesLength, banned phrases, required details, retries
- Sequence logicFollow-ups on a schedule you set
Outputs
- Drafts to approveReviewed before anything sends
- Paced sendingWeekday windows, warm-up per domain
- Replies and intentReplies stop the sequence, opens reach your CRM
Controls
- Your infrastructureYour domains, accounts and cloud
- A person approvesBefore the first send
- Stop rulesRepliers never get another email
What we need from you
- A database, or the data foundation first
- Sending domains and DNS access
- A Google Workspace mailbox for replies
- Your offer, proof points and examples of your tone
Not included
- Guaranteed replies, meetings or revenue
- Buying lists on your behalf
- Ongoing operation, unless scoped
- Deliverability fixes, unless scoped
Does it fit?
Tick the ones that apply to see a verdict.
Not yet if your contact data is thin. Start with the data foundation.
Book a demo call (opens in a new tab)Common questions
Where do the emails send from?
From domains and accounts you own. Your outreach does not run through a shared tool.
Does a person check the emails?
Yes. Rules check each draft for length, banned phrases and required details. A person approves before the first send.
How is it priced?
Custom scope, priced after a short qualification. You get a scope and price before any build.
Do you guarantee replies or meetings?
No. Guaranteed replies, meetings or revenue are not included.
What if my contact data is thin?
Personalization comes from the database, so thin data means thin emails. When a field is unknown, the email leaves it out instead of guessing. If the data is thin, start with the data foundation.