Question 1

What counts as a development request?

Accepted Answer

Almost anything I'd normally quote as a project. Marketing sites, web apps, native iOS and Android builds, AI features, API work, integrations, refactors, performance work, and bug fixes. If it's code, it belongs in the queue. Design work is included when it's in service of what's being built — UI, layout, and design systems, not brand identity or print.

Question 2

Is there a limit to how many requests I can make?

Accepted Answer

No. Queue as many as you want. They get built one at a time, in whatever order you prioritize. You can reorder your queue at any point before a task starts.

Question 3

When will I get my requests back?

Accepted Answer

It depends on the task, which is exactly why every request gets graded. Light tasks land in 1–2 days, standard tasks in about a week, heavy tasks in 2–3 weeks. You see the grade and the delivery date before I start — no vague 'soon.'

Question 4

How does the AI grading actually work?

Accepted Answer

When you submit a request, it's scored against your codebase and a rubric built from real delivery data — scope, unknowns, integration surface, testing burden. The grade and an estimated delivery date come back with the request. I review every grade within a few business hours and confirm or adjust it, and my confirmation is what sets the date. The grader produces the estimate. The commitment is mine.

Question 5

What if I disagree with a grade?

Accepted Answer

Tell me and we'll talk it through. Usually a grade comes back higher than expected because the request is really two or three requests wearing a trenchcoat — split it and each piece gets its own grade and its own date, so the first one is committed while the rest are still being shaped. If the grader got it wrong, I'll override it.

Question 6

Who maintains the code after it ships?

Accepted Answer

I do, for as long as you're subscribed. Bugs in anything I've built for you are fixed free and sit in their own column rather than taking a place in your queue. Dependency bumps, security patches, and small maintenance chores are the same. That's the real difference between this and hiring an agency — you're not buying a handoff, you're renting a developer who stays on the hook for what he shipped.

Question 7

Who actually does the work?

Accepted Answer

I do. AI Solutions Studio is one person — me, Rob. I don't hire out, subcontract, or hand you to an account manager. You work directly with the person writing the code, start to finish.

Question 8

My team already uses AI. Why do I need you?

Accepted Answer

Your team has the same AI I do.

The difference is what it’s pointed at. Aimed at twenty years of shipping production software, it’s leverage. Aimed at a guess, it’s faster guessing — and now there’s more code nobody senior has read.

You’re not buying the tool. You’re buying the aim.

Question 9

What's the stack?

Accepted Answer

Web: Next.js, TypeScript, Postgres, and modern hosted infrastructure. WordPress too — I build on it regularly, and it's often the right call when the people running the site day to day are the ones who have to live in it. Mobile: Expo / React Native, or Flutter when the design system calls for it. AI: the leading model providers plus the orchestration and evaluation tooling around them. Internal systems are in scope as well: I've built a full CRM on Next.js and Supabase, with auth, generated PDFs and Google Sheets sync. Working inside your existing stack is a normal request, not an exception.

Question 10

How do I submit requests?

Accepted Answer

Through your client portal — a live pipeline of your queue, what's in flight, what needs an answer from you, and what shipped. Write the request out, drop in a Loom, link a Figma file, paste a GitHub issue, or forward a customer complaint. If I can understand it, it's a valid request.

Question 11

How does pausing work?

Accepted Answer

Billing runs on 31-day cycles. If you use 21 days and pause, the cycle pauses with you and the remaining 10 days sit there until you come back. Useful when you've cleared your queue and don't have another month of work lined up yet.

Question 12

Who owns the code?

Accepted Answer

You do, from the first commit. Everything lives in your GitHub organization and deploys to your infrastructure under your accounts. Cancel whenever you want and nothing breaks — no proprietary wrapper, no hosting hostage situation, no license to renew.

Question 13

What if I don't like what you build?

Accepted Answer

We revise until it's right. Revisions to a task that's still in flight are part of that task — they don't go to the back of the queue and they don't count as a new request.

Question 14

Are there requests you don't take?

Accepted Answer

Yes. I don't do machine-learning model training or heavy data science, blockchain and smart contracts, native game development, anything requiring a security clearance or on-site presence, or 24/7 on-call coverage. I'm also cautious about adopting large legacy codebases — that's a conversation before you subscribe, not a surprise afterward.

Question 15

Can I subscribe for just one month?

Accepted Answer

Absolutely. Queue up what you need, get it built, and cancel. Come back when you have more. There's no contract and no minimum term.

Question 16

How do I get started?

Accepted Answer

Start with the intake chat — about ten minutes with an AI agent that gets the shape of your first few requests and your codebase. I'll come back within one business day on whether it's a fit. No sales call required.

Unlimiteddevelopment.One price.

You get a grade.Then a date.

Light

Standard

Heavy

Unlimited in.One at a time out.

Your team has the same AI I do.

Things I’veshipped.

Buy / sell / trade CRM

Six Sisters' Meal Planner

Billboard

itisonme.org

One price.No scoping calls.

Pause anytime

You own the code

The awkward questions.