A working AI prototype for your team in 2 weeks.
I build the thing. You decide if it's worth rolling out. If the prototype doesn't prove the business case, you don't pay the back half.
Fixed scope. Fixed price. 50% kickoff. 50% on delivery, and only if it actually works.
Dr. Renaldo "Jonesy" Jones, PMP · Doctor of Strategic Leadership ·
DSL · PMP · Prosci · Army veteran · 2 apps shipped solo
You're not short on AI ideas.
You're short on proof.
I'll be real: most teams I talk to aren't stuck on "what could AI do for us?" They have a whiteboard full of ideas. What they're stuck on is proof.
You've got a workflow (onboarding, triage, proposal drafts, knowledge lookups, whatever it is) and you think AI could cut the time in half. Maybe more. But you can't commit six months and a half-million-dollar budget to "maybe." You can't hand a vendor a blank check and hope the demo holds up in production. And your team doesn't need another slide deck about "AI transformation." They need something they can actually click.
That's the gap I fill.
One workflow. One prototype. Two weeks. Built against your real data, your real users, your real constraints, not a vendor sandbox. When you're done, you either have the proof to scale it, or you have the proof to kill it and move on to the next idea. Either answer is worth the sprint.
The AI Prototype Sprint: fixed scope, fixed price, 2 weeks.
Here's exactly what you get. No bloat. No retainer. No "let's scope it out" for three months and charge you for the meetings.
Not sure a sprint is the right first step? Start with a $2,500 AI Adoption Audit. The fee is credited toward a sprint if you start within 30 days.
Best for: the use case that actually matters, the one that, if it works, unlocks a real decision.
- 20-min scoping call and written brief
- Deeper integration (Notion, SharePoint, a CSV, whatever you've got)
- Prompt library tuned to your domain and your approved tools
- Evaluation rubric your team can run without me in the room
- 60-min stakeholder readout
Best for: the executive sponsor who needs this in front of a leadership team, a board, or a budget committee. The prototype has to hold up under scrutiny.
- Everything in the Prototype Sprint
- Multi-step agent workflow (not just one prompt, a real pipeline)
- Cost + usage tracking so you can model rollout economics
- Governance notes: audit, PII handling, model-fallback logic
- 90-min executive debrief + written rollout recommendation
Integration into your systems, security review and user training.
If the prototype doesn't prove the business case, you don't pay the back half. Read the Sprint Terms
50% on kickoff. 50% on delivery, and only if, on the readout call, you and your stakeholders agree the prototype warrants further investment. If it doesn't, we shake hands, you keep the artifact and the learnings, and we're done. No retainer, no auto-renewal, no ambiguity.
Can't grant a consultant access to your systems? Still fine.
Every sprint above runs at whichever of five access models your security posture allows: full API access, inside your own cloud tenancy, hybrid local-plus-frontier routing, synthetic builds from schemas and screenshots, or fully air-gapped on your hardware. Same sprint, same guarantee, same price card.
Three steps. That's the whole thing.
Scope
You book on Calendly. I come in with structured questions: what workflow, who touches it, what "success" looks like in a number you'd actually defend.
At the end of 20 minutes, we either have a clear sprint scope or we don't. If we don't, no one wastes a dime.
Build
I build. You get async check-ins every 2 to 3 days (shared Notion or private repo) with what shipped and what's blocked.
No 45-minute status calls. No "let's circle back." If I need something from you, I ask once, I ask specifically, and I move on.
Readout
Live demo with you and your stakeholders. I walk you through what the data showed, where the prototype is strong, where it's weak, and what rollout would actually cost.
You leave with three things: the artifact, the evaluation rubric, and an honest recommendation to scale, iterate, or kill.
Why I'm the person to build this.
I'm Dr. Renaldo "Jonesy" Jones: PMP, Doctor of Strategic Leadership, combat veteran (Army, OIF), and a program leader in a large enterprise PMO environment in a safety-critical, regulated industry. I led an enterprise Microsoft Copilot rollout, and I created the RACE framework for AI prompting: Role, Action, Context, Expectation.
Here's what that means in practice. I'm not a vendor pitching you a platform. I'm an operator who runs AI-native workflows every day, and who has shipped two apps solo, RACEprompt on iOS/Android/web and QuietPulse on iOS/Apple Watch, on nights and weekends using the same approach I will use on your prototype. I am also the engineering partner on F3, an app owned by Jada Sullivan. The same stack I'll use to build your prototype.
When I hand you a prototype, it works because I built it the way I build for myself. Production-grade fundamentals, no vendor lock-in theater, honest notes on what AI actually does well and where it's going to disappoint you.
Lead with AI. Not hype.
What you actually walk away with.
Every sprint ships the same shape of artifact. The details change with the use case. Here's a sample of what a Prototype Sprint delivers.
Illustrative example, not a client result. This is a representative composite showing the shape of a Prototype Sprint deliverable. All numbers are examples.
Sales proposal first-draft generator
The workflow we prototyped
Sales reps spend ~3 hours drafting the first version of each proposal. 40% of those drafts get killed before the client sees them. Goal: cut first-draft time to under 30 minutes without dropping close-rate.
What I built
- A web tool where a rep pastes discovery-call notes + selects a deal tier
- Agent pipeline: extracts requirements → pulls the right case studies from a Notion knowledge base → drafts a RACE-structured proposal → flags sections that need human judgment
- Evaluation rubric: 12 blind-graded draft comparisons (AI-assisted vs. rep from scratch) scored on accuracy, tone, completeness
- Cost model: ~$0.14 per draft at current API pricing; breakeven at ~4 min of rep time saved per proposal
What a readout can show
- First-draft time: 3 hrs → 38 min on average (-78%)
- Close-rate: held flat over 31 proposals (within margin of error, not a drop)
- Rep satisfaction: 8/10 would keep using it; 2/10 wanted tighter tone control → addressed in rollout plan
What I handed off
- The working prototype (deployed, logins for 3 users)
- A 7-page rollout doc: what to scale, what to tighten, what's out of scope until Sprint 2
- The RACE prompt library (yours to own, no licensing attached)
Built for one kind of team.
- Companies in the 500 to 5,000 employee range: big enough that AI adoption has real stakes, small enough that we can move without a steering committee.
- VP of Learning & Development, VP of Innovation, or Director of Digital Transformation: the person who owns an AI pilot budget and has to defend the ROI.
- Teams with one specific workflow in mind: not "help us figure out our AI strategy" (that's different work, and I can point you to people who do that).
I'm not built for enterprise procurement cycles. I'm not built for "let's do a 6-month discovery." If that's what you need, I'm the wrong fit, and I'll tell you on the scoping call.
Questions I get a lot.
Looking for open-ended strategy consulting instead of a fixed-scope sprint? See Strategy Advisory →
Retainer-shaped work: embedded partner, quarterly engagement, roadmap across multiple systems. Different product, different cadence.