A working prototype
Built on the software you already have. Usable by the team member you named at kickoff, on day one of week six.
One real AI use case, six focused weeks, a working prototype your team can defend at the next board meeting. No deck, no proof of concept that goes nowhere.
Not sure? Take our free 2-minute AI assessment. You'll get a clear read on whether the pilot is the right next step.
Every pilot ends with the same five things in your hands. No "executive insights," no theoretical models. Things your staff can use on Monday.
Built on the software you already have. Usable by the team member you named at kickoff, on day one of week six.
Agreed on at kickoff, measured at the end. Something a board member would recognize: hours saved, dollars raised, applications processed, families served.
If the prototype works, this is the plan to put it in front of more of your team. Step by step. With effort estimates and decision points.
How the prototype works, what it relies on, where to look when something breaks. Written for the program staffer who'll inherit it, not for engineers.
A 60-minute working session walking your leadership team and (if you want) your board through the prototype, the result against the success metric, and the recommendation on whether to scale.
The same proven sequence we use across every Rapid AI Pilot, sized to a nonprofit team's pace.
Six-week sprint
Week 1 · Discovery
Lock the use case, agree on the success metric, identify your team's named owner.
Weeks 2–3 · Data & design
Pull the data we need, design the approach, validate the architecture against your existing software.
Weeks 4–5 · Build & test
Build the prototype in weekly increments. Demo every Friday. Adjust based on what your team sees.
Week 6 · Handoff
Final readout. Documentation handed over. Your owner takes the keys. Engagement ends.
We don't bill by the hour and we don't pad scope. You'll know the number before you sign.
Rapid AI Pilot
$50,000 to $80,000
Fixed fee. Includes all five deliverables, the leadership readout, and the optional board readout.
We don't sell software, we don't bill ongoing licensing, and we're not waiting in the wings to charge you for support. Here's what happens when our six weeks are up.
Code, models, documentation, accounts. Everything we built belongs to your organization. Built to run on the software you already pay for, with no recurring fees to us.
The 90-day roadmap is yours to execute in-house. If you'd like ongoing senior data leadership while you do, look at Fractional Data Leadership. Optional, separately scoped.
Sixty days after the readout, we get on a 30-minute call with your team to see how the prototype is performing in production. No hidden invoice. It's part of every pilot.
It happens. The success metric is set up front, so we'll know clearly. If the prototype misses the mark, the readout includes the honest reasons why and what we'd recommend instead. You still own everything we built and everything we learned.
No, but it helps. If you already know the use case and have an executive sponsor who can make decisions in the room, you can go straight into the pilot. If not, the audit is a faster, cheaper way to find the right starting point.
Yes, when it's the right tool. Many of our pilots use large language models for tasks like summarization, classification, and intake. We'll only recommend it when it's responsible, when your data policy allows it, and when it solves the actual problem.
A regional nonprofit ran a six-week engagement with us that reduced their manual reporting time by 60%, freeing program staff to spend more time on mission delivery. We're publishing more case studies as engagements close. See the full set on Insights.
Book a 30-minute scoping call with a senior principal. We'll know in the first 15 minutes whether your idea is pilot-ready.