The bar of critical systems
15 years in regulated fintech and nearly 30 building software. That standard for quality and security is what I bring to your decisions.
Service · Technical consulting
Senior judgment for the technical decisions that cost the most.
I work with your team on three fronts: architecture and technical decisions, bringing AI into development with a serious process, and visibility into your systems in production. Your team builds; I bring nearly 30 years of judgment, review what gets produced —including what AI generates— and get hands-on where it counts.
The context
Your team is rarely short on hands. It's short on judgment.
AI made writing code cheap, but it didn't make deciding what to build — or how — any cheaper. An architecture that won't scale, an AI rollout that adds debt instead of speed, a critical system nobody can diagnose when it breaks: those decisions get paid for over years. That's where someone who has worked on systems that can't afford mistakes makes the difference — not by replacing your team, but by giving it direction.
Six things I do differently.
You talk to the person who decides
No account managers or junior consultants in between: the judgment you hire is the judgment working on your case.
Hands on the code when it matters
This isn't slide-deck consulting. If a decision needs a proof of concept or a critical piece to be validated, I build it.
Recommendations that get executed
Every recommendation comes with its rationale, its cost and how to verify it was applied correctly. No reports that end up in a drawer.
On top of what you already have
I work on your current stack —.NET, Java, GeneXus, SQL Server, whatever you run—. I don't propose throwing away what works.
I use what I recommend
My AI development process is out in the open: Fetchpier, an open-source API client, is built with it, and its code and its gates can be audited.
Where I can help.
Architecture and technical decisions
Architecture reviews, a second opinion before an expensive decision, stack choices and legacy modernization without a big bang. Also as a part-time technical lead, if your team doesn't have one.
AI-assisted development, with process
How to bring assistants and agents into development without losing quality: requirements, plans, review and verification. Including a close look at what AI is writing into your codebase.
Visibility in production
Making your critical .NET, Java or GeneXus systems diagnosable: logs, metrics, traces and monitored business rules, built on OpenTelemetry with OpenSearch or Elastic.
From the first conversation to decisions your team can act on.
- 01
Assessment
I get to know your system, your team and the problem that brings you here. I come out with an assessment and a concrete, fixed-price scope proposal.
- 02
Prioritized recommendations
What to do, in what order and why. Each item with its impact, its effort and how to verify it was applied correctly.
- 03
Hands-on support
I work alongside your team while it executes: reviews, decisions along the way and, when needed, the proof of concept or critical piece that unblocks the rest.
- 04
Handoff
I document the decisions and their reasoning so your team can carry on alone. If you'd rather, I stay on as technical lead with an agreed commitment.
This service is for you — or it isn't.
I'd rather say no than oversell. If something here doesn't add up for you, we'll talk it through on the first call.
It makes sense if…
- You're facing an expensive technical decision —architecture, stack, migration— and want a senior second opinion before committing.
- Your team already uses AI to build software and you want it to add speed without adding technical debt.
- You run critical systems in production and, when something breaks, figuring out what happened takes hours or days.
- Your team has no senior technical lead and you need one part-time.
It's not for you if…
- You need someone to build your whole product: I don't take on full development projects, though I can help you define it and choose who builds it.
- You need to add developers to your team by the hour: I don't do staff augmentation, and I'm happy to refer you to someone.
- You want a report to tick a box and file away: what I deliver is meant to be acted on.
What people ask me before we start.
How is this different from a traditional consultancy?
Two things. You work directly with the person who has the judgment, with no layers in between. And I don't stop at recommendations: if a decision needs to be validated with code, I write it.
Will you build the product?
Not the whole product: that's for your team or the vendor you choose. What I do is implement focused pieces when they add value —a proof of concept, a critical piece, the architectural foundation— and support the team while it builds.
What technologies do you work with?
The ones you already have: .NET, Java, GeneXus, SQL Server, Postgres, TypeScript. When the work is about visibility in production, the foundation is OpenTelemetry with OpenSearch or Elastic. The rule never changes: I don't propose throwing away what works.
How is it priced?
The initial assessment is fixed-price. From there we agree on a clear scope and price for each stage, with no open-ended hours.
Do you have GeneXus experience?
Yes: I've been speaking at GeneXus community events since 2003 and won the GeneXus Challenge twice. If what you need is an in-depth review of a KB, that's what the GeneXus KB audit is for.
Other services
Got a technical decision on your plate?
One first conversation is enough to know whether I can help. If it makes sense, I'll propose a fixed-price assessment to get started.