Advisory engagements where structural diagnosis, market repositioning and platform strategy moved the needle — documented from the inside.
These are real advisory projects — not anonymized hypotheticals. Each one informed a specific dimension of the G.E.A.R. model. The structural patterns that emerged across both engagements are what this consulting practice is built on.
The client was a technically strong automated financial reconciliation platform, built and launched in Uruguay, that had developed genuine traction with payment-adjacent companies in the local market. The founding team wanted to expand into Spain and Europe — a significantly larger, more regulated and more competitive market.
The challenge wasn't the product itself. The platform processed up to 1,000 transactions per second, had over 300 active users and was handling more than 16M monthly transactions with 95%+ automated reconciliation rates. The challenge was structural: the platform was positioned as a bank reconciliation tool in a market full of accounting software and ERPs doing basic reconciliation as a feature.
Entering Spain with that positioning meant competing on price with entrenched generic solutions — a race to the bottom that would have destroyed the margin the product deserved.
The G.E.A.R. diagnostic identified two compounding structural gaps:
Revenue gap: The platform was priced and packaged as a reconciliation utility when it was operating as data infrastructure for its best clients — managing data lineage, transformation, enrichment, governance workflows and real-time discrepancy alerting well beyond what any ERP offered. The value delivered significantly exceeded the value claimed.
Architecture gap: The platform narrative led with the reconciliation use case — which triggered a comparison with tools designed for accountants. The actual architecture (any-data ingestion, no-code governance, multi-company/multi-currency, 1,000 TPS) positioned the platform firmly as a data operations layer — but that story wasn't being told.
This engagement is a live example of the Revenue and Architecture dimensions of G.E.A.R. working in tandem. The product was strong — the structural gap was in how that strength was communicated, packaged and targeted. The intervention didn't change the product. It changed the frame.
"The most dangerous position for a strong product is a weak category. The platform was solving a data operations problem while being perceived as an accounting utility. The intervention was to realign the narrative with the actual problem being solved — and the buyer who experienced it most acutely."
The client came to me as an independent Tech Advisor with a compelling creative concept — a collaborative narrative platform built around the "6 words" format (inspired by Hemingway, Monterroso and Wired's editorial tradition), designed for Generation Z users aged 17–28.
The founding team had a strong cultural insight and a clear target audience. What they needed was a structured approach to validate the concept before committing significant technical resources — and a technology architecture recommendation that balanced Web3 ambitions with MVP pragmatism.
The structural challenge was common in early-stage Web3 consumer products: the technical vision (blockchain-native, token-incentivized participation) was significantly more complex than the validation stage warranted. Building for the end state before validating the core engagement hypothesis would create technical debt and slow the critical early feedback loops.
I designed and facilitated a 5-day Design Sprint (September 8–12, 2025) to validate the core engagement hypothesis and define the MVP scope before any significant technical investment.
The sprint produced three critical outputs: a validated user engagement hypothesis (the "6 words" format resonated strongly with Gen Z testers, producing near-unanimous stated intent to engage), a clear identification of the execution gaps (UX confusion, broken onboarding flow, visual monotony) that needed resolving before any scaling, and an updated probability assessment — concept validation at 90%, 30-day retention potential revised upward to 65% with UX fixes applied.
The testing also confirmed one non-obvious finding: the platform's social purpose dimension — enabling creative participation around cultural references — resonated more strongly with the Gen Z testers than the gamification or monetization mechanics. This was a positioning insight that needed to lead the product narrative.
Based on the sprint findings, I delivered a formal MVP Technology Advisory document with a phased architecture designed to validate fast and scale when earned — not before.
The advisory intervention here was an Architecture dimension problem: the founding team's natural instinct was to build toward their end-state vision. The structural recommendation was to decouple the validation architecture from the production architecture — and only bridge to Web3 when the engagement data made it structurally justified, not aspirationally motivated.
This is the difference between building infrastructure for a platform that exists and building infrastructure for a platform you hope will exist.
"Web3 features are architecture decisions, not product decisions. Building them before the engagement hypothesis is validated inverts the risk profile — you're committing to infrastructure complexity before you know if the core experience warrants it. The recommendation was to earn the blockchain layer through validation data, not assume it."
Before any recommendation, a focused diagnostic identifies the real structural constraint — not the symptom being managed. In both engagements, the surface problem was different from the structural problem. This phase takes 1–3 sessions and produces a written misalignment map.
One structural problem, one focused intervention. the first client needed repositioning and market entry strategy. the second client needed architecture de-risking and validation design. Scope discipline prevents the diffusion of effort that dilutes impact in advisory work.
Recommendations don't end in a document. Both engagements involved working alongside the teams through execution — adjusting in real time as the market, users and organization responded to structural change. The advisory artifact is a record, not the deliverable.
One focused conversation to map where the misalignment lives. No commitment required beyond that conversation.