Foresight Software — Jaime Gómez Moreno
I build digital products, and the factory that builds them.
I work with founders in three ways: as a consultant, when the question is still what to build; as a builder, when what you need is the thing itself, delivered; and through Advance, the factory I built to do this work — which you can learn to drive yourself.
Arrived from the footer of a site I delivered? That site was built this way — one person, one line at a time, with a factory of my own doing the holding.
Software will eat the world,
AI will eat software,
yet here we are, talking about software.
Everything you make is a digital product. Your onboarding is a product. Your quoting sheet is a product. The way a client finds you, pays you, and comes back is a product. Most founders don't see it that way, so they hire out the parts that look like "software" and hand-run the rest forever.
The moment you do see it, the constraint stops being can this be built and becomes how fast can I try things. That is the only question this work is about, and the answer is a system — not a smarter prompt. That's what I sell, in whichever of the three shapes fits you.
What I've built
Six recent things, and who they were for.
All since June 2026, each with how long it took to have something live. Three go unnamed, by agreement: for those I give the industry and the problem.
Memory and community
Or Haneshama · for a client
A service for adopting the memory of a person murdered in the Shoah, with a published catalog of more than fifteen thousand names.
34 days from the first change to the client's own domain
Commerce inside streaming
Unnamed, by agreement
A store that lives inside the video: the subscriber sees something they like and buys it right there. Behind it sits a full commerce platform.
16 days from the first change to running in the cloud
Customs and foreign trade
Unnamed, by agreement
The infrastructure a customs broker uses to send messages to U.S. Customs and read what comes back, with a dashboard that shows how far each one got.
235 cycles in 56 working days
Field operations
Electolab · built with a team
A territorial intelligence platform: field teams, data capture and real-time analytics, with a mobile app made for long shifts and weak signal.
33 cycles of mine, within the team's
Mobile games
Unnamed, by agreement
A physics puzzle-platformer for phones, in pre-production. The game is someone else's; what I build is how the controls feel.
A running prototype on day two
Design tools
gridhero · my own product
A tool for drawing interfaces by dragging edges; what's left exports as a page that stands on its own.
Published the day it started
A cycle is a finished change: made, verified, and shipped into the product. The figures were measured on October 6, 2026, from each project's history.
And from further back, five years in television
Amazon Comcast Red Bull
Companies I made smart TV and streaming-device apps for, as a technical product manager.
How we can work together
Three ways in, depending on where you are.
They're the same practice seen from different distances. Start wherever you are — plenty of people arrive at one and end up at another.
As a consultant
When the question isn't how to build it but what to build, and whether it should exist. I read what you already have, sit with your operation, and tell you what I'd do — including when the answer is "not software". Short engagements, written conclusions you can hand to whoever builds it.
As a builder
When you need the thing itself. I build and deliver it — sites, internal tools, the product you've been putting off — in the open, where you can read the work as it happens instead of waiting for a demo. Fixed scope, real deadlines, and the code is yours from day one.
With my tool
When you'd rather build it yourself and what's missing is the machinery. Advance is the factory I use every day: I set it up on a box that's yours, teach you to drive it in ten hours, and keep it healthy. You stop hiring the building out.
Most projects run five weeks and cost US$1,000.
The work moves in short cycles: we sit down for an hour, and the next day you have something you can use — not a plan, not a mockup — already with a round of my own adjustments on it. You use it, tell me what's missing, and the next one starts from there.
It can be more or less depending on the project. That comes out of the first call, which costs nothing. Book the call →
Advance has its own pricing. See Advance →
The thinking behind it
I've been writing about this loop for a while.
Bring the thing you've been putting off.
Forty minutes on my calendar, no charge and no commitment: tell me what you'd build if building were cheap, and I'll tell you which of the three ways fits it. If you'd rather write first, jaime@foresight.software.
Book your slot