Skip to content

Library

Read more of our work.

FAQ

The questions worth asking before you build with AI.

How much do I have to pay?

We create bespoke work, so pricing depends on the specific engagement. Typical builds start at $3,000 USD and can go as high as $15,000 USD depending on complexity. Consultation sprints, which are multi-session and multi-week engagements, start at $2,000 USD, while one-off sessions are priced differently. Before work starts, you'll know the scope, milestone plan, approval criteria, and price.

How do I know this won't become another expensive AI experiment?

We start with the business case before the build, tied to specific, measurable KPIs. If a workflow, asset, or automation does not have a clear metric attached, we do not force AI into it. We choose the smallest useful system that can create a real outcome, then build from there.

What if I don't like what you build?

We work through deliverables and milestones, so you approve each meaningful step before money changes hands. Every deliverable has approval criteria tied to the project spec, which keeps feedback grounded in the agreed scope. If something misses the mark, we revise it within those boundaries before moving forward.

What if I don't know exactly what I need yet?

That's normal, and it's why discovery comes first. You don't need to arrive with a perfect spec or a list of tools. You need enough context for us to understand your offer, your workflow, and where the business feels heavier than it should.

What happens if the system breaks, drifts, or stops being useful?

We build with resilience in mind, so systems are stress-tested during the build phase before handoff. We test expected use cases, edge cases, failure points, and drift risks so the system is less likely to break under normal use. External changes, like platform updates, API changes, or new tool limits, can't be guaranteed forever. If your engagement includes ongoing implementation support, we monitor, maintain, and fix issues as they come up so the system keeps working in real conditions.

How do you handle sensitive business or client information?

We treat data access as a design decision, not a casual upload. The work starts by identifying what the system truly needs, what should stay private, and where human review belongs. When client-facing or sensitive workflows are involved, we design guardrails around inputs, outputs, permissions, and review points before anything goes live.

What do I actually get at the end?

You get the finished asset or system, plus the context needed to keep using it. Depending on the engagement, that may include documentation, walkthroughs, workflow maps, prompts, templates, implementation notes, or support during the first stretch of use. If you want continued maintenance, we can handle the technical upkeep for an ongoing fee, so you keep getting the benefit of the build without becoming its operator. The goal is not dependency; it's a system you understand, own, and can improve.

Work with us

Have a workflow, offer, or asset that should work harder for you?

Bring us the messy source material, repeated bottleneck, or half-built idea. We'll help identify the system worth building first.

Prefer direct email? james@unpromptable.dev

This was actually the first time I submitted an article that came back with no comments from QA at all - which honestly blew my mind a little. The AI system definitely played a big part in that. It made the writing process smoother and more natural, especially when trying to strike that conversational, human tone.
Islam AshrafResearcher, LMSL
James Presbitero Jr.

James Presbitero Jr.

Strategist and writer. Sharpens positioning, offer logic, voice systems, and the founder thinking the AI has to preserve.

Jenny Ouyang

Jenny Ouyang

Builder and operator. Designs the workflows, delivery, and documentation that turn a build into a system the business can actually run.