Daniel PaoBook intro

Engagements

Fixed scope.
Yours at the end.

Every engagement starts with a free 20-minute intro call, so nobody pays to find out we're a bad fit. I quote after that call — a two-client agency and a twenty-client agency need different machines, and a headline price would be a lie about one of them.

01Two shapes

EngagementMost commonInfrastructure buildFractional GTM engineer
Shapetypically 4–10 weeksQuoted after the intro callmonthly, cancel any monthQuoted after the intro call
What it isI build the machine end to end, in your stack, under your brand, and hand it over.Ongoing engineering capacity: extend the machine, add clients, fix what breaks.
Includes
  • Fixed scope and a fixed price agreed before the first commit
  • Direct work in your repos and vendor accounts
  • Sourcing → enrichment → drafting → approval → send → reporting, wired and tested
  • Client onboarding path so the next logo is a form, not a project
  • Documentation, walkthrough, and a handoff your team can actually run
  • A set block of build time each month, scheduled with you
  • New client onboarding and per-client configuration
  • Provider changes, migrations, and deliverability upkeep
  • Async access for the questions that would otherwise stall a week
  • No notice period and no minimum term
Best forAn agency with signed clients and a delivery model that doesn't survive the next five.Agencies growing client count faster than they can hire an engineer.
Scope itScope it

02Terms

The fine print

How pricing works
Builds are fixed-price against a written scope agreed before the first commit — if the scope grows, we re-price it in writing, not at the end. The retainer is monthly with no minimum term.
Ownership
You own everything I build, including the code, outright. It lives in your repos and your vendor accounts from day one. I reuse my own patterns across engagements; your client data, ICPs, and configuration never leave your stack.
White-label
The default. What I build carries your brand, and I'm happy to be invisible to your clients. If you'd rather introduce me as your engineer on a call, that works too.
Conflicts
I decline work that directly conflicts with an active client, and I'll name the conflict before taking anything on. I'm also building my own GTM platform — I'll say so on the first call so you can judge it yourself.
Access and security
I work in your accounts under your SSO with least-privilege access, and I'll sign your NDA and MSA. Credentials stay in your vault, never in a repo or a spreadsheet.
Handoff
Every build ends with documentation, a walkthrough with whoever owns it, and a defined support window. If you never need me again, the engagement worked.

Next step

Not sure which one you need?

Book the intro call. It's free, it's 20 minutes, and you'll leave knowing what I'd build first.