Supernova was founded in 2018 by two tech-savvy founders who were obsessed with building software and wanted to understand what made some products succeed while others disappeared.

In the beginning, our role was relatively simple. A client would come to us with an idea, a specification, or a list of features, and we would turn it into working software. We spent those early years becoming better engineers, learning how to move quickly, solve technical problems, and ship reliably.

During that period, we built more than 128 web applications around digital commerce. Together, those products generated more than 7 million leads across core markets including the US, Canada, Europe, and Australia, and over $12 million in client revenue, with some still generating more than $120,000 MRR.

Those numbers mattered, but what interested us more was why some of those products performed significantly better than others.

The code was not always the difference.

Two products could be engineered equally well and still produce very different outcomes. One could find demand, acquire customers, generate revenue, and continue growing. Another could be technically sound and struggle almost immediately.

That raised a more important question for us: if engineering alone did not determine whether a product succeeded, what did?

At the time, our experience was much stronger in engineering than product management. We knew how to build what had been requested. What we increasingly wanted to understand was everything that happened before the request became a specification.

Was the underlying problem real? Who experienced it strongly enough to care? Was the proposed solution actually the right one? What assumptions were being treated as facts? What did the first version really need to prove? And once customers started using the product, what would make them return, pay, recommend it, and eventually allow a business to grow around it?

Those questions gradually changed the kind of company we wanted Supernova to become.

We started moving upstream.

Instead of entering only when the requirements were already decided, we became more involved in the research, strategy, customer problem, business model, and product decisions that shaped those requirements in the first place.

This was a harder role to take on. Writing code against a defined scope gives you a relatively clear measure of completion. Product decisions are less comfortable. They require judgement, incomplete information, customer evidence, commercial thinking, technical understanding, and a willingness to challenge assumptions before significant time and capital are committed.

But we came to believe that this was where much of the real leverage existed.

A strong engineering team can build almost anything. The more important question is whether it should be built at all, what version should be built first, and whether the resulting product creates enough value for customers and the business to justify everything that comes next.

As our thinking evolved, so did the products and systems we worked on.

We moved from standalone web applications into SaaS products across web and mobile, and later into AI, cloud, data, and infrastructure. Our role expanded with them, from research and product strategy through design and engineering to launch, growth, scaling, and increasingly complex technical systems.

That evolution is what shaped Supernova into a Product Studio.

Today, Supernova has two connected focuses: services and products.

Through our services, we work with founders and product teams across the lifecycle of a software business. Sometimes that means determining whether an opportunity is worth pursuing before serious investment begins. Sometimes it means turning a validated opportunity into a production-ready product. Sometimes the product already exists and the challenge becomes activation, retention, growth, scale, or the engineering systems underneath it.

The problem changes. Our underlying approach does not.

We use the same product principles, engineering disciplines, operating methods, and increasingly AI-enabled ways of working across our engagements. That matters because we do not want the knowledge created on one project to disappear when that project ends.

We want it to compound.

Every product exposes us to a different market, customer, business model, technical constraint, growth problem, or operating challenge. What we learn becomes part of the way we approach the next one. Over years, that accumulation of decisions, mistakes, patterns, tools, systems, and judgement becomes considerably more valuable than any individual technology or framework.

At the same time, we are applying those same principles to products of our own.

We think this is an important part of the model.

It is easy to advise someone to invest another month in development when it is not your capital. It is easy to recommend a feature when you will not have to acquire the customers who use it. And it is easy to talk about product-market fit, retention, pricing, and growth when someone else ultimately carries the consequences.

Building our own products puts us on the other side of those decisions.

The capital matters. The priorities matter. The customer matters. A feature that does not create value becomes a real cost. A wrong assumption creates real consequences. And every decision forces us to confront the same question our clients face: is this actually worth building?

We believe the two sides of Supernova make each other stronger.

Client work gives us exposure to industries, founders, business models, technologies, customers, and engineering problems that would be difficult to encounter inside a single company. Building our own products forces us to experience the consequences of product decisions directly.

The learning moves in both directions.

And as software development changes again through AI, increasingly capable models, agentic systems, and new ways of designing and engineering products, we think that combination becomes even more important. The ability to produce software is becoming faster and more accessible. The difficult part is increasingly deciding what deserves to be built, how it should work, where technology creates meaningful leverage, and how all of it translates into something customers genuinely value.

We are eight years into building Supernova this way, and the company continues to evolve with the technology and the products around us.

The tools will change. The types of products we build will change. The way software companies are created will almost certainly change.

But the underlying idea behind Supernova has become much clearer:

understand the problem deeply, make the important decisions early, build with conviction, learn from what happens in the real world, and carry those lessons into whatever we build next.