(The first paid step)

The $2,500 discovery

A discovery is $2,500 and takes about two weeks. It ends with the quantified annual dollar value of your best workflow, the arithmetic behind that number, and the written acceptance test any software has to pass. Run from Orange County, California, remote across the US. If it doesn't surface 10x the fee, you don't pay.

Two weeks on one workflow. You end up with a dollar figure you can defend and a written test the software has to pass.

$2,500Flat fee, about two weeks
10xValue threshold, or no fee
~6 hrsOf your team's time, total
4Documents you keep either way

(The cost)

What is a discovery and what does it cost?

Two weeks, $2,500, one workflow. Usually the one bleeding the most money, mapped end to end with the people who actually run it.

You get the annual dollar value of fixing that workflow, with the arithmetic on the page so your CFO can argue with it. You get the acceptance test: the written conditions software has to meet before anyone gets to call it done. That's the product. No maturity model, no deck about your future.

Plenty of AI money gets committed before anyone checks the arithmetic. Pertama Partners' 2026 roundup found 42% of AI projects return zero ROI, and 61% of the projects approved on projected ROI were never measured after launch. A number nobody checks isn't really a number. Discovery exists to produce one you can check later, against reality.

(What you get)

What do you actually get for $2,500?

Four documents. Plain language, no jargon tax.

  1. The workflow map. Every step, who does it, how long it takes, and the three or four places it stalls. Drawn from watching the work, not from an org chart.
  2. The annual dollar value, with the arithmetic shown. Hours times rate times volume, plus rework and error cost, minus what a fix would actually cover. Every input is your number, sourced in the session, not our estimate of your business.
  3. The written acceptance test. The conditions the software has to pass to count as finished. Written before anyone quotes a build, which is the only time it can be written honestly.
  4. The recommendation. Sometimes that recommendation is don't build this. Fix the process, or buy the $80-a-month tool that already does most of it.

All four are yours the day of the readout. See what a build looks like if the answer turns out to be software.

(The guarantee)

What happens if it isn't worth it?

If discovery doesn't surface at least 10x the fee in quantified annual value, you don't pay.

Read that precisely, because it's precise. The threshold is $25,000 a year in value we can show the arithmetic for. Find it, and the fee stands. Don't find it, and there's no fee, and you keep the map anyway.

The guarantee covers the value, not the build. Say the two weeks turn up $400,000 of annual value and the honest recommendation is to fix the process rather than buy software. Guarantee met, fee stands. You paid $2,500 to not spend a build budget. If the value isn't there at 10x, that's our miss and we eat it.

(The two weeks)

What are the two weeks like?

Five steps, about six hours of your team's time in total.

  1. Intake call, 60 minutes. What hurts, who feels it, what you've already tried. Enough to pick the workflow worth two weeks.
  2. Workflow mapping, days two to five. We sit with the people who do the work and watch the real steps. That includes the spreadsheet nobody mentions in meetings.
  3. The numbers session. Whoever owns the budget, in a room, agreeing to the inputs before we do the multiplication. Value nobody signed off on is a guess.
  4. Drafting the acceptance test. Written down and sent for redlines while the workflow is still fresh in everyone's head.
  5. The readout, 90 minutes. Documents in your inbox two days before, so the meeting is arguing about the number rather than hearing it for the first time.

Week one earns its keep on data alone. Gartner puts 85% of AI project failures on data quality, and IDC has 65% of companies citing data readiness as the blocker. Both are cheaper to discover in a mapping session than in month four of a build.

(Free scoping vs. discovery)

How is this different from a free scoping call?
  Free vendor scoping call Internal analysis Portillo discovery
What it costs $0, plus four hours of your senior people Salary you're already paying, plus the work that stops while it happens $2,500 flat, waived if the 10x threshold isn't met
Who it serves The vendor's pipeline. The scope fits what they sell. The team writing it, and whichever department has the most pull You. The recommendation can be to build nothing.
What you keep A proposal written to be accepted Whatever got written down, if anyone wrote it down Map, valuation, acceptance test, recommendation. Take them anywhere.
How the number is verified Vendor's estimate of your savings Internal estimate, rarely audited after launch Your hours and rates, arithmetic shown, signed off before the readout
What it produces next A statement of work A slide that circulates for a quarter A test the software has to pass, or a documented reason to stop

Nobody's being dishonest in column one. A free scope is a sales document, and it does its job well. It just isn't a deliverable, and you can't take it to another firm.

(Why pay)

Why pay for discovery when other firms scope for free?

Because the free version can't say no. MIT's NANDA report found 95% of enterprise AI pilots deliver no measurable P&L return. Those pilots weren't scoped by fools. They were scoped by people whose next invoice depended on the answer being yes.

Paying for the analysis buys the option of a bad answer. It also buys documents that exist independently of us: the workflow map is true whether or not you ever hire anyone, and the acceptance test is a fair bar for any vendor you hand it to.

$2,500 is priced to be small next to the mistake it prevents. Build bands start at $5,000 for a narrow integration and clear $250,000 at the complex end. Two weeks of thinking against that is not a hard trade, and if the thinking doesn't pay for itself you don't pay for the thinking.

(After discovery)

What does the build cost after discovery?

Builds are priced at 10 to 20% of the measured annual value, never by the hour. Hourly billing pays us for slow. The percentage only works because discovery produced a real number first.

WorkRange
Custom web app or line-of-business systemMVP $15k–75k. Complex $250k+.
AI or LLM integrationStrategy or pilot $5k–25k. Mid-size $25k–100k.
RAG or knowledge copilotBuild $8k–45k, plus $650–1,750/month operations.
AI consulting retainerFrom $2,500/month.
AIOps / automation retainer$2k–15k/month.

Every build carries the same promise: we work it until it passes your acceptance test. That promise is only safe to make because the test was written in week two, by both of us, before any money moved.

The engineers who map your workflow are the ones who build it. Nothing is thrown over a wall to a separate delivery group, and your account doesn't get handed to a junior once the paperwork is signed. We keep the number of live engagements deliberately small so that stays true, which sometimes means a start date six weeks out. We'll tell you that at the readout rather than after you've signed. What you get in exchange is in MIT's numbers: buying from a specialized vendor ships a working AI system about 67% of the time, roughly twice the rate of building it internally. Groovyweb's 2026 build-versus-buy breakdown puts an in-house AI team at $1M to $1.8M loaded in year one, with three to six months of ramp before it produces anything.

(No lock-in)

Are you locked in after discovery?

No, and the documents are built to make leaving easy. The map, the valuation and the acceptance test are written to be read by anyone. Hand them to another firm or to your own team. The acceptance test in particular is portable on purpose: it's the fairest way to hold any vendor to a result.

If you do build with us, the code is yours outright. It isn't resold to your competitors, it isn't licensed back to you, and there's no hosting arrangement designed to make leaving painful. You get the repository.

There's no retainer attached to discovery either, and no automatic anything. Two weeks, four documents, done. Whatever happens next is a separate decision made with better information. If you'd rather see how we work before spending anything, the AI Pilot Autopsy is free. Two pages, emailed back as a PDF, nothing to fill in and no sequence afterwards.

(Not a fit)

Who this isn't for
  • You already know exactly what to build and want hands. Then discovery is $2,500 of confirming what you know. Skip it. Send us the spec and let's talk about the build instead.
  • You can't get an executive in a room for two weeks. The numbers session needs whoever owns the budget. Without that signature the valuation is just our opinion with a dollar sign on it, and the guarantee becomes unmeasurable.
  • You want the fee credited against a build you haven't agreed to. That turns discovery into a deposit, and a deposit bends the answer toward build. The independence is the thing you're buying.
  • You want a second opinion to win an internal argument. We're not for rent as ammunition. The recommendation lands where the numbers land, which may be squarely on the side you were hoping to beat.
  • You need it next week. Discoveries get scheduled, and the next start is usually a few weeks out. More on how we say no in Not Us.

(Common questions)

Common questions before booking

Is the discovery fee credited toward a build?

No. Discovery is priced on its own because it stands on its own. Crediting it would make it a deposit, and a deposit quietly pushes the answer toward build. The whole point is that don't build this stays a live option on the last page.

How much of your team's time does it take?

Roughly six hours across two weeks, spread over four or five people. The executive who owns the budget needs to be in two of those sessions. The people who actually run the workflow need to be in the mapping session, because they are the ones who know where it really stalls.

Can a discovery run remotely?

Yes. Most of it happens on video and works fine across the US. If you are in Orange County, the mapping session is better in person, and Irvine, Newport Beach, Costa Mesa, Santa Ana, Anaheim, Tustin and Huntington Beach are all a short drive.

What if our data is a mess?

That is the normal case, and it is worth knowing before you spend build money. Gartner puts 85% of AI project failures on data quality. The workflow map names the gaps it finds, and the acceptance test is written so the software has to pass with your real data, not a clean sample.

Is there a contract?

A short written agreement covering scope, confidentiality, and the 10x guarantee. Nothing recurring and nothing to cancel. Because the guarantee is in writing, the fee settles after the readout, once you have the documents and can see whether the number is there.

How do you start a discovery?

Email Portillo Technologies at [email protected] with the workflow that is costing you the most. If you have an AI pilot that already stalled, ask for the AI Pilot Autopsy first. It is free, it is two pages, and it will tell you whether a discovery is even the right next step.

More on the thinking behind all of this: AI consulting in Orange County.

(Sources)

Sources
  1. MIT NANDA report, 2025, on enterprise AI pilots and P&L return, and on specialized-vendor versus internal build success rates. softwareseni.com
  2. Gartner and IDC figures on data quality and data readiness in failed AI projects; zero-ROI and unmeasured-ROI project rates. pertamapartners.com
  3. In-house AI team cost and ramp time, year one. groovyweb.co

(Book it)

Bring us the workflow that costs you the most

One email with the workflow and roughly what it costs you. We'll tell you whether it's worth two weeks, and we'll say no if it isn't. If a pilot already stalled, start with the free autopsy instead.

Replies inside two business days, from Jason, not a sales queue.

Direct: [email protected]