AI Prototype Sprint

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 ·
Microsoft Copilot Champion · Anthropic Claude Champion · 3 apps shipped across iOS, Android, web

3
production apps shipped
iOS · Android · Watch · Mac · Web
10
agents in my AI dev team
same architecture I'll build for you
11
languages in production
EN · FR · DE · JA · KO · PT-BR · ES-MX · SV · IT · NL · ZH
50/50
payment guarantee
back half only if it proves out
Not a vendor pitching you a platform. An operator running an AI-native workflow inside a real enterprise, every day, with three shipped products as the proof.

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.

Two sprints at a time. If both slots are full when you book, you go on the waitlist — I'll tell you exactly where you are in line.

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.

Micro Sprint
$5,000
1 week · one workflow · one prototype

Best for: validating a single, scoped use case fast. Think — "can AI draft the first pass of this one report?" or "can it triage these specific tickets?"

  • 20-min scoping call + written brief
  • One working prototype (web app, internal tool, or agent workflow)
  • Live walkthrough demo
  • Handoff doc + 30-min Q&A with your team
Full Scope
$15,000
3–4 weeks · multi-step workflow + governance

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 Standard
  • 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

If the prototype doesn't prove the business case, you don't pay the back half.

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.

Three steps. That's the whole thing.

Day 0

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.

Week 1–2 (up to 4 for Full Scope)

Build

I build. You get async check-ins every 2–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.

End of sprint

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 full-time program director at a Fortune 1000 industrial company. I'm also Microsoft's Copilot Champion and Anthropic's Claude Champion, and the creator of 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 an AI-native workflow inside a real enterprise every day, and who happens to have shipped three apps — RACEprompt on iOS/Android/web, QuietPulse on iOS/Apple Watch, and F3 on iOS/Android — on nights and weekends using 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 Standard Sprint delivers.

Standard Sprint · $10K · 2 weeks

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 the readout showed

  • 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)

This is a representative composite — every sprint ships the same shape of artifact, customized to your workflow.

Built for one kind of team.

  • Companies in the 500–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 Fortune 500 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.

The guarantee

If the prototype doesn’t prove the
business case, you don’t pay the
back half.

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.

This isn’t hype — it’s aligned incentives. If the sprint doesn’t produce proof, I don’t deserve the back-half check.

Questions I get a lot.

Yes — within reason. Notion, SharePoint, Google Drive, a CSV, an internal API — if you can get it to me, I can wire the prototype to it. For anything behind a VPN or requiring custom auth, we scope a secure-transfer pattern in the kickoff call. I've built against Cloudflare Workers, OpenAI, Anthropic, and local Ollama models — the stack flexes to what your security team can greenlight.
Depends on the use case. Most sprints end up running Claude (Anthropic) or GPT-4-class models for the heavy lifting, with a local fallback (Ollama + qwen2.5 or similar) for cost-control on high-volume calls. I'll recommend the right stack on the scoping call and document the economics at readout.
You own it. Full stop. Code, prompts, RACE framework library, evaluation rubric — all yours. No licensing, no platform lock-in, no "call us to scale." If you want to bring me back for Sprint 2 (rollout, scaling, integration), we scope it separately. If you want to hand it to your in-house engineering team and take it from there, that's fine too — the handoff doc is built for that.
That's a strategy question, not a build question — and it's the wrong reason to hire me. If you're not sure which workflow to prototype, I'll tell you on the scoping call, and I can point you to AI-strategy consultants who do that work well. When you know the workflow, come back and we'll sprint it.
Because the scope is tight by design. One workflow, one prototype, one decision at the end — that's it. I'm not trying to build your whole AI roadmap in 2 weeks. I'm trying to prove or disprove one business case so you can make the next decision with real evidence. That's what makes 2 weeks work.
That's the whole guarantee. 50% on kickoff covers the scoping, the build, the readout, and the artifact. The back 50% only ships if, on the readout call, you and your stakeholders agree the prototype proved the business case. If it didn't — you keep the prototype, you keep the learnings, we part on good terms, and I eat the back half. This isn't hype — it's aligned incentives. If the sprint doesn't produce proof, I don't deserve the back-half check.
A builder on a fixed-scope sprint. Not a consultant. Not a staff-aug contractor. I write a statement of work, I deliver against it, we both sign the readout, and the engagement closes. If you need advisory after — speaking, keynote, quarterly review — that's a different conversation with a different price.
Generally yes — Full Scope tier is built for this. I run workflows against customer data regularly, and we can structure the build to stay inside your cloud (AWS, GCP, Azure — or self-hosted on Ollama). If your security team needs to review the setup, bring them on the scoping call. I won't try to sell around them.

Ready to prove the business case?

One workflow. Two weeks. Honest answer at the end.

Book your 20-min scoping call → Back to Home

Or send me a note directly — me@drjonesy.com. Tell me the workflow you're thinking about. I'll respond within 24 hours.

Wrong lane?

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.