Accepting new projects for January

From brain-dump
to reality in days.

My friend and I sketched an idea over coffee at Waffle House. Zero code. 8 hours later: wired prototype, live on a dev site, breathing. That's what a Napkin Session delivers.

If all you have is a sketch on a napkin, that's perfect. We can start from there.

AI-Native Velocity

10-20x faster than traditional dev. I use advanced AI agents to compress weeks of work into hours.

I built an AI-native project management system that lives in the repo alongside the code. Every decision documented. Every session logged.

Stack: Agnostic. We use whatever language the AI writes best.

Strategic Execution

I'm a CTO who builds. You get 20 years of Business Analysis and Project Management experience baked into every line of code.

Tangible Artifacts

No fluff. You walk away with assets you own: a working prototype, a private repo, and a clear roadmap document.

The Origin Story

It started at a Waffle House.

A friend of mine carried an idea in his head for ten years. He put time to it and some money to it, but he didn't know how to code and didn't want to invest the money that traditional development required to get him to a prototype. We had discussed it years ago, but it was just an idea.

When I started to get into AI, I remembered that meeting and I brought it up. We met at a Waffle House, scribbled the core of his idea on a napkin, and then we talked it out on a Zoom call as I vibe coded the prototype. We identified the data we wanted, built the interface, wired it together, and then launched a prototype that worked in about 8 hours.

That single moment—the shocked look on his face when he realized that we could do this, that he could do this—is why Napkin Sessions exist. Sometimes you don't need a roadmap. You need ignition.

The original napkin sketch for College Decoded

I don't bill hours. I bill complexity delivered.

Story points measure scope and complexity — not time. A 3 SP task costs the same whether it takes me 20 minutes or 2 hours. That efficiency is my margin, not your discount.

STEP 1

Napkin Session

Free / 30 min

We sketch it out. I estimate story points. You get clarity.

Clarity on what you're trying to build
Honest assessment of fit
Story point estimate and budget range
Book a Free Session
STEP 2

Business Case

$2,500 - $5,000

Make it real. You left the napkin session with clarity — now you need the document that gets stakeholders to say yes.

Executive summary & problem framing
Cost-benefit analysis with real numbers
Implementation roadmap (1-2 weeks detail)
ROI framework for decision-makers
Book a Napkin Session
STEP 3

Builds

$100 - $150 / Story Point

Ready to go? I build it. Working software, not decks.

SP Range Rate/SP
1 - 50 SP $150 / SP
51 - 200 SP $125 / SP
200+ SP $100 / SP

Fixed quote provided after Napkin Session.

"Be brief, be brilliant, be gone."

- Woodrow Wilson

I don't do endless discovery calls. If you send me information up front, I will come prepared.

Based in Nashville? I'll meet you in person.
Remote? We'll do a Zoom/Google Meet. Every call is recorded and transcribed with AI so we don't miss a detail.

How it works

  • 1

    Napkin Session (Free)

    Book a call. Share your idea. We map it out together. You leave with clarity and a scope.

  • 2

    Business Case ($2,500-5K)

    Need buy-in first? I formalize the idea with numbers, risks, and a roadmap your stakeholders can approve.

  • 3

    Build ($100-150/SP)

    Ready to go? I build it. Working software, not decks.

FAQ

Everything you need to know about how I work.

How do story points work?

Story points measure complexity, not time. A task's points reflect how much work it involves, how many unknowns exist, and how likely it is to need rework.

Points What it means Example
1-2 Trivial/Small Fix a typo, add a form field
3 Medium New component, API endpoint
5 Large New page, auth flow
8 Very Large Major feature, architectural change
13 Epic Needs to be broken down first

I estimate story points during the napkin session. You'll know the scope and budget before we start.

What's included in the price?

  • Working, deployed software
  • Handoff documentation
  • Session logs showing exactly what was built

Not included: ongoing hosting costs, third-party service fees, maintenance after handoff.

How long does a build take?

Depends on scope. Rough guide:

  • 50 SP project 2-3 weeks
  • 150 SP project 4-6 weeks
  • 500+ SP multiple months

I ship to production same-day when possible. No "planning sprints."

Do you offer ongoing support?

For most builds, no — I hand off working software and you're done.

If you need ongoing technical leadership, that's fractional CTO work. We can discuss a retainer, but it's a different engagement.

What tech stack do you use?

Technology-agnostic — I pick what fits the problem, not what I know best.

Common choices: Astro, React, Node, Python, Supabase, Cloudflare, Azure.

What if my project changes mid-build?

Scope changes happen. We re-estimate the new work with story points and adjust the budget accordingly. No surprises.

Bert Carroll

I'm Bert Carroll.

I'm a CTO today, but I've spent 20 years building things—as a Business Analyst, Project Manager, and IT Manager. Based in Nashville, I combine that career's worth of experience with the latest AI coding tools to build software at speeds that shouldn't be possible.