The Brainz Framework · In action
Eighteen processes rebuilt. Six companies. The same loop.
Every process, tagged by the move that rebuilt it.
The framework, not the slide
Each row below is a real process inside a real company — and the move that rebuilt it.
18
Documented outcomes across the engagements below
6
Companies — mobility, B2B SaaS, enterprise, industrial, legal, marketing
7/7
Moves of the framework, each represented multiple times
10 yr
Longest active relationship (ROEPA, since 2016)
I
Picap · Mobility, five countries
A regional platform crossing the line from startup to platform.
Head of Engineering. Consumer mobility across five countries, each with its own unit economics and regulatory context. Read the full case →
-
Moves 02 · 04
The C-suite needed a credible forecast — not a story. Drivers, riders, revenue, cohort retention.
We did. Built a monthly C-suite forecast scorecard bottom-up from cohort retention, revenue, and rider/driver metrics. Outcome. The C-suite got a credible monthly number for the first time — built bottom-up from the data, not from optimism. Plannable.
-
Moves 01 · 05
The engineering function had to absorb growth and keep it steady, across five countries with different unit economics.
We did. Hired, structured the team for multi-country operations; defined what Head of Engineering meant in a startup-to-platform transition. Outcome. 1M+ monthly rides — sustained, consumer-grade volume across the region.
-
Move 06
Maintaining 99.9% uptime at consumer-mobility scale across a multi-country, multi-stack, multi-stake environment.
We did. A hundred decisions about caching, queues, observability, and pager rotations — done correctly the first time. Outcome. 99.9% uptime sustained across the region; architectural decisions still load-bearing.
-
Moves 05 · 06
Same product, five different unit economics, five different regulatory contexts — motion was re-invented per market.
We did. Documented the revenue motion once, then re-ran it across geographies without re-inventing per market. Outcome. 5 countries onboarded without re-architecting per market.
-
Moves 06 · 07
Cloud and engineering costs were growing faster than rides — the platform had outgrown the cost model it started on.
We did. Re-architected the parts of the system that compounded the bill — observability, caching, queues, and the steps that should run on managed infra versus our own. Pointed the metrics at the invoice, not just the latency. Outcome. −45% development cost · −60% cloud spend. Sustained, not a one-off.
II
Fluyenta · B2B SaaS, workflow automation
A revenue motion re-anchored on what the buyer is actually buying.
COO → Head of Innovation. Buyer-centric Plays replaced feature pitches; the motion outlived the consultants. Read the full case →
-
Moves 01 · 03 · 05
The revenue motion was selling on feature parity rather than on buyer value.
We did. Rebuilt the Discovery question bank around the buyer's actual procurement context — cost of waiting, renewal dynamics, the decision they were really making. Stopped pitching features. Outcome. 3× average deal size · −40% sales cycle.
-
Moves 05 · 06
The operating structure predated the plan the company was actually running.
We did. Lined the operating structure up with the plan in fifteen days — focused around the people and functions carrying the roadmap. Outcome. Structure aligned to the plan in 15 days. Focused around the work carrying the roadmap.
-
Moves 04 · 06
Ramp time for new reps and consistency on playbook execution were the levers with the most upside.
We did. Shipped a documented AI product surface (Axon) paired with the SPARC methodology and Claude in the loop. The team learned a new build cadence. Outcome. Axon shipped; team certified on the new motion; same headcount shipping more than before.
-
Moves 05 · 06
The revenue motion had room to travel better across markets — discovery and the close sequence varied by team.
We did. Certified managers across EMEA and LATAM on the same playbook, in two regulatory and cultural contexts. Outcome. 14-person revenue rollout. Manager certification installed. The team can re-run the playbook without us.
III
Enterprise SaaS · Enterprise, EMEA + LATAM
A solid product, and a motion rebuilt to travel across two regions.
Operator on a multi-year rebuild. Two regions on one buyer-side playbook. Read the full case →
-
Moves 01 · 05
Rep ramp time and manager consistency across EMEA and LATAM were the two biggest available levers.
We did. Created a documented onboarding loop tied to real Plays — the buyer-side motion — not slides or war stories. Outcome. Ramp time halved.
-
Moves 02 · 05
Sales conversations were anchored on what the platform could do, not on what the buyer was buying.
We did. Re-anchored conversations on the buyer's procurement context — cost of waiting, renewal-cycle dynamics with and without us. Outcome. 2× quota attainment in the cycle. Buyer-side Plays installed across the floor.
-
Moves 04 · 07
Protecting the renewal base across two regions was the foundation everything else would stand on.
We did. Certified managers across two regions on the same playbook; installed a weekly Renewals Sync discipline. Outcome. 0 renewals lost in the period. Floor first, new logo second.
Different sector each time. The same loop. The artifact stayed.
The framework, in action · Six companies, eighteen processes
IV
ROEPA · Industrial services, France + Spain
The test of architectural decisions made well, ten years ago.
Director of IT, developer, systems maintainer — since 2016. The relationship is worth more than the hours. Read the full case →
-
Moves 06 · 07
Multi-site, multi-country industrial-services operations required sustained system architecture and near-zero downtime.
We did. Built a Rails + DigitalOcean foundation in 2016; maintained for ten years with near-zero drama. Outcome. 10-year active relationship. Two countries. Decisions from 2016 still load-bearing in 2026.
-
Move 07
A decade-long relationship to protect — deliberately low-touch, high-trust.
We did. Stayed deliberately near-passive — the relationship is what we protect, not the hours. Outcome. ~8 h/mo current touch. Earned the right to debut Nexus, our AI seller, on the most trusted ground we have.
V
LexPro · Legal tech, Colombia
Pricing validated by the buyer, not the seller.
Portfolio product. Independent Colombian lawyers running on email, Word, and spreadsheets; corporate suites are built and priced for a different kind of firm.
-
Moves 03 · 06
Independent Colombian lawyers ran their entire practice on email, Word, and spreadsheets; corporate legal suites are built and priced for much larger firms.
We did. Shipped a working case-management + time-tracking + AI-research product before the pricing question — Rails + iOS + Android + Word add-in, built with Claude in the loop. Outcome. 16+ firms registered on the free tier. Eight lawyers at AGM Abogados running an active PoC since May 2026.
-
Move 02
The product pricing was undervalued; there was no market signal for what firms would actually pay.
We did. Asked the cost-of-waiting question instead of feature-request questions. Firms named the monthly figure themselves. Outcome. 10× pricing validated. The original plan was undervaluing the product by an order of magnitude.
VI
Amplifica · Marketing, generative design
Targets first. Then we let the model score anything.
Portfolio product, operated by Daniela Calvano. Live at amplifica.studio.
-
Moves 05 · 06
Generative-design tools are fast — but speed alone doesn't tell a marketer which draft will actually perform.
We did. Built the virality-scoring engine (TRIBE v2 — LLaMA 3.2-3B + fMRI brain encoding) before the UI. The scoring engine is the moat — defensible, brain-encoded. Outcome. 0–100 virality score on every draft. Three design directions per brief — reel, carousel, static, email, banner. Nine drafts/day on the Pro tier.
-
Moves 02 · 07
Risk that AI-generated output isn't actually useful for brand marketing — speed without signal.
We did. Dogfooded the product against our own brand (Lumina Fragancias) before selling externally — if Amplifica can't grow Lumina, it can't grow paying clients. Outcome. Live at amplifica.studio. Paying tiers (Solo, Pro); monthly cancel-anytime. Video generation in private beta.
The same loop, in your company
Name a stuck process. We'll quantify the cost.
Companion is a 12-week engagement on the seven-move loop. First process live by week six — measured against targets your leadership signed off on before any agent was written.