for
Prepared for Tim Muret, CMO

One data layer.
Every gift, traceable to the life it changed.

The five systems in the briefs you sent — a data foundation, a dashboard, a donor-prospecting pipeline, a media system, and a relationship platform — all reading from the same source of truth. Here's what's already proven, what we'd build, and what we'd nail down together first.

4working prototypes already built in-house
5systems in your briefs, one shared foundation
1canonical record per donor, gift, and story
DASHBOARD DONOR PROSPECTING MEDIA LIBRARY RELATIONSHIP PLATFORM IMPACT REPORTS UNIFIED DATA LAYER

Tim — this walks through what we saw in the packet you put together: the April MVP, Tony's videos, the data-layer thinking, and the five briefs, in order. Rather than send back a generic pitch, we wanted to show you exactly what's already working, what we'd build next, and what we'd need to nail down together before either of us puts a number on it. Read it in whatever order makes sense to you.

Already proven

This isn't a "could this work" conversation anymore.

Before any of this was formally scoped, your team had already hand-built and shipped four working prototypes. That's rare — and it changes what this engagement actually is: not "can we build it," but "how do we make it run without Tony rebuilding it by hand for every donor."

Live · April

The MVP donor impact report

A single donor's gift traced to fifty named families freed from bonded labor — story, stats, and faces, built as a private page for one gift.

"Response from the donor was terrific."
June

The major donor workspace

A concept for a living donor profile — memory, context, and an auto-generated impact report and proposal drawn straight from one donor's giving history.

June

Rapid-response impact reports

A faster version of the same idea, built for any gift — even one-time gifts — as a retention moment, not just a quarterly ritual.

Live campaign tooling

Donor proposals at scale

Seven versions of one real campaign proposal, tuned by donor tier, with name-personalization already working end to end.

Every one of these was built by hand, one donor or one campaign at a time — and that's the point: the hard part, proving what donors actually respond to, is already done, by your team. What's left is production engineering — pipelines, permissions, monitoring, upkeep — so this works for every donor without becoming Tony's second full-time job. That's a different kind of work than proving it, and it's the work we do.

The system

One foundation. Four things built on top of it.

Every one of the five briefs you sent depends on the same missing piece: a single record connecting donor, gift, project, beneficiary, and story. Build that once, and each of the four systems on top of it gets cheaper and faster to ship. It's the same pattern we run our own business on — one record underneath, every dashboard, pipeline, and portal reading from it.

FOUNDATION

Unified data layer

One system that knows, for every dollar given, exactly which donor gave it and what it funded — so every surface built on top of it inherits that connection automatically instead of re-stitching it by hand.

01

Performance dashboard

Always-on visibility into what's driving results, with plain-language explanations of what changed and why — no more waiting days for a hand-built report.

02

Major donor prospecting

A steady, scored flow of qualified major-donor prospects with a verified, warm way to reach them — reps start warm, not cold.

03

Smart media library

Every photo and video pre-tagged and pre-linked to the project and impact report it belongs to — no more hunting for the right asset.

04

Relationship platform

Major, mid-level, field-partner, and influencer relationships, each on its own purpose-built surface, all reading from the same record — so nothing falls through the cracks as the roster grows.

Sequencing

How we'd build it

Discovery goes first, and it's deliberately small. Then the foundation — paired with a fast, visible win, so nobody waits months to see something real. Each step is priced and gated on its own: you can stop after any of them and keep everything it shipped.

FIRST

A short discovery sprint, before either of us commits to the full build

Two to four weeks, fixed price, fixed deliverables: what Salesforce actually allows, how clean the gift-and-project data really is, where an existing tool beats a custom build, the governance groundwork below — and a plan with a firm number on each step instead of a range.

STEP 1

Foundation, plus one visible win

Stand up the unified data layer while wiring the proposal tool that's already built to real data for one live campaign — so there's a real result in weeks, not just infrastructure underneath it. No real donor or beneficiary data flows until the safeguards agreed in discovery are in place: that gate is part of the build, not a promise beside it.

STEP 2

Two fast wins, in parallel

The performance dashboard and the major-donor prospecting pipeline both sit directly on the foundation and ship independently — proving value to both the budget side and the gift-officer side at once.

STEP 3

Smart media library

Ingest and tag the existing media library, and link every asset to the project and report it belongs to.

STEP 4

Relationship platform, one workspace at a time

Ship the major-donor workspace first, since it's already validated internally — then extend to mid-level, field-partner, and influencer only as each proves out.

What we'd nail down together first

Three things, before either of us commits to numbers

What Salesforce will actually let us connect to

You run on Salesforce, and that integration is the one genuinely new piece here — the honest unknown in any estimate. The discovery review — not a request for access today — tells us what your setup actually allows and what should simply live inside Salesforce itself. The goal is one source of truth, not a second CRM on the side.

A simple rule for anything AI touches before a donor sees it

Your AI Subcommittee already started this conversation — we'd work inside it, not around it. The rule we'd propose is simple: a person signs off on every AI-drafted report before it goes out, and no real donor or beneficiary data moves until the right data-handling agreement is in place. We'd bring the same pre-deployment checklist we run our own AI systems against.

Protection for the people in the stories

Some of what you hold names survivors and field partners in regions where exposure is dangerous. Before any of it enters any system, we'd agree together on what gets stored, what gets masked, who can see it — and which links should never sit in one system at all. That applies to the prototypes that already exist, not just what we'd build. Beneficiary safety is a design constraint from day one, not a policy bolted on later.

Tim — let's talk about what's first.

We'd rather walk through the build sequence with you and Michael — a fixed price on the discovery step, honest ranges for the rest — than leave this as an open-ended idea.

hello@techhub.us