Should-Build Sprint
Fixed-fee diligence and product discovery. Should this exist? Can it be built? What would it take—and what would make it fail?
- Problem framing
- Technical feasibility
- Risk map
- Build plan
Fixed fee
1–3 weeks
1–3 weeks
Technical product studio
We turn difficult ideas and broken systems into things that actually work.
We build our own products, and we help companies turn difficult ideas and broken systems into working ones. From first signal to real users, we bring product judgment, architecture, integration, security, and AI-enabled execution to the work.
I make complex systems actually work in the real world.
Ghost in the machine / 04signal present
InputUnclear idea
ProcessFind the signal
OutputWorking product
Build more value with less waste
EnergyInfrastructureMoneyHuman attention
01 / The between-space
The important idea is usually hiding between the boxes.
Not purely product. Not purely engineering. Not a clean strategy problem or a clean implementation problem. The opportunity lives in the seams—and those seams are where most teams lose the signal.
Sometimes a company knows what it wants. Sometimes it only knows something should exist.
We make the ambiguity useful: determine what should be built, test the hard assumptions, prototype the right thing, connect it to real systems, and carry it through production.
AI gives a small, experienced builder dramatically more execution leverage than the old large-team model. The measure is not how complicated the tooling looks; it is judgment, speed, and useful things shipped.
Good engineering is resource stewardship. We favor systems that create more value with less waste—of energy, infrastructure, money, and human attention. Reliable power, clean water, efficient compute, and resilient environments are foundations, not side causes.
Boundary mapLook between layers
ProductWhat should exist
SystemsWhat must connect
IntelligenceWhat can accelerate
RealityWhat must survive
Signal →
working product
working product
02 / Studio model
Four ways a difficult idea becomes real.
Start with the smallest engagement that can produce evidence. Build only when the signal survives contact with reality.
Build to production
Prototype fast, connect to real systems, solve the hard details, and ship it live. We build what we recommend—and tell you when you should not build it.
- Product prototype
- Architecture
- Integration
- Production launch
Project
Outcome-bound
Outcome-bound
Technical ownership
Fractional architecture plus ongoing responsibility for the system: decisions, reliability, security, vendors, roadmap, and the seams nobody else owns.
- Architecture counsel
- Operating rhythm
- Team leverage
- System stewardship
Recurring
Senior-led
Senior-led
Product participation
When discovery reveals a repeatable, standalone product, we can take less cash to keep a stake in what gets built—through licensing, revenue share, partnership, or selective equity.
- Selective only
- Aligned economics
- Shared upside
- Evidence first
Deal by deal
Not a fund
Not a fund
Find the shortest credible path from idea → working artifact → real user → revenue. Then stay with the winners long enough to finish them.
DON’T PROVE SOPHISTICATION BY MAKING THINGS DIFFICULT / BUILD ONLY WHAT EARNS ITS COMPUTE, INFRASTRUCTURE, ENERGY, MONEY & ATTENTIONSolve the valuable problem first.
Start where a real customer has real urgency and budget. No studio theater, trend-chasing, or invented demand.
Notice what repeats.
Look across engagements for the workflow, integration, capability, or risk that keeps appearing in different clothes.
Productize only with evidence.
Turn proven patterns into reusable tools or standalone products when the economics and demand are visible.
Keep the upside when it earns the risk.
Use licensing, partnerships, revenue share, or equity selectively—not as a substitute for getting paid.
03 / Pattern library
We’ve seen this movie. The details change. The failure patterns do not.
Credibility here is not a logo wall. It is the range to recognize what is actually happening across the system—and the judgment to do something useful about it.
The prototype that cannot cross into production
Promising software meets identity, security, operations, data access, and enterprise constraints.
The integration that is actually five systems
Frontend, gateway, identity provider, network edge, and backend each look healthy in isolation.
The internal tool quietly becoming a product
A repeated operational problem reveals demand well beyond the team that first felt it.
The enterprise promise outrunning the platform
Sales has found the market. Now architecture, reliability, and security must catch up without stopping momentum.
The AI demo with a missing operating model
The model works. The real product still needs evaluation, guardrails, access control, observability, integration, and ownership.
Range, not résumé.
15+ years building and shipping startup products, enterprise systems, integrations, mobile and web applications, open-source software, and energy-sector technology—followed by deep work in identity, security, cloud, production reliability, and utility systems.
Public work where it matters.
PWA open-source maintenance, technical publishing, and conference speaking sit alongside years spent making complicated systems hold together beyond the demo. AI now compresses the path from judgment to working artifact; experience decides what is worth shipping and what can survive production.
04 / GhostOp Labs
Put the idea in public. Build around real demand.
Products in public / maturity labeled
Labs is where strong product concepts meet reality early. We publish the idea, prototype the useful core, attract users and design partners, and invest deeper only when the demand is real.
Idea → prototype → interest → design partners → demand → build. No finished-product theater.
Source Select
Visual control over how AI uses your sources.
A working interface for choosing sources and tuning retrieval, behavior, parameters, and presets. Source Select makes the controls behind AI answers visible and usable instead of burying them behind provider tooling.
- Choose and control sources
- Tune retrieval behavior
- Adjust model parameters
- Save reusable presets
- Inspect source-backed answers
Open Working Prototype
Live at selectsource.ai. Use it, test it, and tell us where it earns a place.
TrustNode
Trusted enterprise knowledge, with receipts.
A trusted enterprise knowledge layer over documentation, tickets, APIs, architecture notes, runbooks, and tribal knowledge. Answers stay grounded in sources while respecting provenance, permissions, freshness, and conflicting information.
- Source-backed answers
- Permission-aware retrieval
- Freshness and stale-document checks
- Conflict detection across sources
- Architecture and service mapping
Become a design partner and help define the first useful version.
AuthTrace
See exactly where authentication breaks.
Visual debugging and intelligence for OAuth, OIDC, and PKCE flows. AuthTrace maps the full chain—tokens, redirects, cookies, CORS, gateways, WAF/APIM, and browser or mobile differences—then explains where it failed and why.
- OAuth, OIDC, and PKCE flow mapping
- Token and redirect failures
- Cookie, SameSite, and CORS failures
- WAF and APIM interference
- Mobile, browser, and IdP differences
Become a design partner and test it against real auth failures.
05 / Field notes
What we notice from inside the machine.
Essays on architecture, technical diligence, fragile builds, and the gap between what software promises and what the organization can actually operate.
The Demo Works. The Build Doesn’t.
A polished demo can conceal brittle architecture, improvised operations, and risk that only appears when real users and systems arrive.
Read the field noteFor funds and portfolio teams, when relevant
Technical diligence when the decision matters. Senior execution when the portfolio needs it.
GhostOp can assess the product and technical reality before a decision, then help founders and operators act on what the diligence reveals. The work stays centered on useful products, capable teams, and evidence from real users.
Demand over theater. Diligence and build work are services to the company and its customers—not a substitute for proving the product.
Something is trying to get built.
Bring the product idea, the broken system, or the workflow nobody has made tractable yet. We’ll find the smallest credible move toward something users can test—and favor systems that waste less compute, infrastructure, energy, money, and human attention.