THE PROJECT FIELDBOOK · AI / CRM / DATA / OPERATIONS

Built in support of growth.

Real problems from growth-stage companies—from the operating plan down to the systems that run it. Each case is a short read: the situation, what we built inside the team's own tools, and what changed.

SELECTED FIELDWORK / 00—15
THE BUILD PHILOSOPHY

Not recommendations.
Operating leverage.

The pattern repeats across every one: a real business problem, off-the-shelf software that either falls short or costs too much, and a focused build inside the tools already in place. Call it the 80% build—the workflow the team needs, production controls around it, and none of the unused enterprise suite.

Client names and proprietary details are withheld under confidentiality. Build stage is labeled on every case; numbers appear only where source records support them.

SELECTED PROJECT SPOTLIGHTS

SITUATIONBUILDCHANGESAFEGUARDSDELIVERED
FIELD / 00 · FLAGSHIPExecutive planning + build
A bookings target, turned into the meetings this quarter depends on.

From a board bookings target to the capacity model, weekly dashboards, and outbound engine that deliver it.

GTM operating system
FIELD / 01Production
A scoring agent that can show its work.

An AI agent that researches and scores 16,822 accounts—and shows the evidence behind every score.

AI account scoring
FIELD / 02Analytical system
Turning CRM history into an ICP the field can use.

Years of CRM history turned into a defensible answer to "who is our ideal customer."

Ideal customer analysis
FIELD / 03Production
One clear status for every lead.

Five tools' worth of seller signals, one trustworthy status on every lead.

Lead status + follow-up
FIELD / 04Production
Territories that survive planning season.

Fair territories built from real opportunity—and executed in the CRM, not a spreadsheet.

Territory design
FIELD / 05Controlled rollout
One CRM for the whole customer operation.

A company that outgrew its startup tooling—60 Monday boards moved into HubSpot without flattening the business.

CRM migration to HubSpot
FIELD / 06Production
Pipeline and activity truth, inside Salesforce.

Pipeline coverage and rep activity, live inside Salesforce—no weekly workbook.

Pipeline dashboards in Salesforce
FIELD / 07Salesforce build
From pricing spreadsheet to guided quoting.

Volume pricing, guarded discounts, and branded order forms—without buying CPQ.

Quoting + deal controls
FIELD / 08Research prototype
A research agent that knows where the claim must stop.

1.85M rows of public data distilled into claims a founder can defend.

AI market research
FIELD / 09Production systems
Making every handoff visible, not magical.

Handoffs between CRM, support, and outreach made observable—and recoverable.

Connected systems + alerts
FIELD / 10Product platform
Turning the work RevOps repeats every week into a product.

The work RevOps repeats every week, productized with previews and rollback.

RevOps toolkit
FIELD / 11Build + validation
Pipeline credit you can defend.

A marketing attribution system built inside Salesforce and HubSpot—every number on the dashboard traceable to the touches behind it.

Marketing attribution
FIELD / 12Staged migration
Two CRMs become one, without losing the customer.

An acquired company's HubSpot—customers, pipeline, and consent—folded into the acquirer's Salesforce without losing a thread.

Acquisition CRM integration
FIELD / 13Controlled rollout
Matching that understands the org chart.

Every inbound lead routed to the right facility among 8,740 healthcare accounts—and every match shows how it was decided.

Lead-to-account matching
FIELD / 14Production
Support that understands the org chart.

The right support account, created for the right company the moment a deal closes—and checked every hour after that.

Support + CRM sync
FIELD / 15Controlled rollout
A startup's CRM, upgraded to run the company.

Live product data plus custom apps inside HubSpot—a growth-stage operating platform without an enterprise suite.

Custom HubSpot apps

MORE FROM THE BUILD LOG

The smaller systems matter too.

01

CAMPAIGN ATTRIBUTION

Which campaigns actually create pipeline

Marketing was spending real money with no defensible answer to what it produced. Every call, meeting, and email reply now rolls up into a clean view of which campaigns influenced which deals — reporting leadership can take straight to the board.

02

REVENUE REPORTING

One set of revenue numbers everyone trusts

The CRM said one thing, the dashboards said another, and finance lost days reconciling the two. Now there is a single agreed path from where a number is entered to where leadership reads it, with a named owner for every metric.

03

SALES TO CUSTOMER SUCCESS

A handoff that doesn't drop the customer

Closed deals were landing on Customer Success with half the story missing, so onboarding started with an apology. Every handoff now carries what was sold, who owns the account, and proof the transition actually happened.

04

DUPLICATE CUSTOMERS

One customer, one record

The same customer showed up three different ways across systems, inflating counts and muddying renewals. Records were matched carefully, look-alikes set aside for review instead of merged blindly, and a person makes the final call on anything unclear.

05

COMPETITIVE INTELLIGENCE

Public evidence on competitors, on tap

Sales kept losing to competitors nobody was tracking. A quiet research tool now scans public web records for competitor customers and moves, keeps the evidence behind every finding, and reports what changed since the last look.

06

CUSTOMER HEALTH

Early warning before a renewal goes sideways

Generic account scores flagged nothing until a customer was already gone. Health signals are now built from how each kind of customer actually uses and pays for the product, so the team sees churn risk and expansion openings months earlier.

07

DEAL DESK

Pricing policy the CRM actually enforces

Discount rules lived in people's heads, and every quote turned into a negotiation with finance after the fact. Deals now move inside approved pricing limits with the right sign-offs, clean customer documents, and clear criteria for when a pilot converts.

08

SYSTEM SWITCHOVER

Moving to a new system with a way back

Moving years of live customer data to a new system is where growth companies get burned. This one was rehearsed first, moved in small batches, checked line by line, and kept fully reversible until everything proved out.

BUILT AT THE ALTITUDE REQUIRED

ExecutiveStrategy · planning · decisions
OperationalProcess · policy · cadence
TechnicalData · systems · code

The advantage is moving between all three without losing the operating thread.

GROWTH STUCK SOMEWHERE?

Bring one revenue bottleneck. In thirty minutes we'll decide what it needs.

Start the conversation