Skip to content

product inception

Work out what to build first

A product inception is the short piece of work before a software build, when a team works out what to build, what it depends on, and roughly what it will cost. Ours ends in a clickable prototype of the key parts of your product and a written recommendation. One to three weeks. Starting at $10,000.

what you get

A prototype you can click, not a longer document

You make the build decision with the prototype in hand and a short memo any team can build from. Product Inception fits when the problem is clear and the first version is not.

  • Clickable prototype

    We build a prototype because people react to one more honestly. Objections, missing context, and bad assumptions show up faster this way.

  • Implementation memo

    What to build first, how to build it, what to leave out, the main technical risks, and how to proceed.

  • Scope boundary

    What belongs in the first serious build, what should wait, and what should stay out.

  • Next step

    A clear recommendation to build, change direction, or pause.

how it runs

The work moves from unknown to decision

Inception ends when the next decision is clear. We don't design the whole product. We find out what a full build depends on.

  1. step 01

    Fit call

    We talk through the opportunity with you, and decide together if House of Giants is the right fit.

    Checkpoint: Buy an Inception

  2. step 02

    Source review

    Once we have the go-ahead, we'll absorb the material you already have and map the customer, the workflow, the product promise, and the constraints.

    Checkpoint: Alignment on the problem and the key questions

  3. step 03

    Prototype pass

    We design and build the key parts of the product, the parts people must see working before anyone commits.

    Checkpoint: Clickable prototype

  4. step 04

    Stakeholder review

    We put the prototype in front of your stakeholders. We then surface objections, missing context, buyer reactions, and implementation traps.

    Checkpoint: Feedback and refinement

  5. step 05

    Implementation memo

    We turn the prototype work into the memo. Decisions, main risks, what to leave out, dependencies, and next steps.

    Checkpoint: Build or pause

  6. step 06

    Readout

    We walk through what the prototype showed us. We work through what is still unknown, and give you confidence that the path you choose is correct.

    Checkpoint: Assurance that you're making the right decision

three questions

A prototype is useful only if it changes the decision

The prototype gives everyone something concrete to react to. The product story, the expensive technical unknowns, and the commercial case. These three questions run through the whole engagement.

  1. Product

    Does this create the right kind of value for the right audience?

  2. Technical

    Where could the architecture or integrations create expensive surprises?

  3. Commercial

    Is the opportunity strong enough to justify a complete build?

the terms

The prototype and the memo are yours, even if the build isn't ours

Product Inception is not a down payment. Here are three terms to know before you pay.

  • What you own

    The prototype and the memo, outright, once the invoice is paid. Both work without us. If another team or your own engineers do the build, the memo is still the plan.

  • What the prototype isn't

    Production software. Nothing real runs behind it, with no live accounts and no live data, and you don't launch it. It is also not proof that customers want the product, not investor approval, and not a full security audit. It helps you make the build decision.

  • What it commits you to

    Nothing past the readout. Pause, build elsewhere, and continue with HoG are all valid endings. The recommendation follows the evidence, not the sale. If you build with us, it starts from the decisions in the memo.

the right fit

Who it's for

Product Inception is for a serious software product that isn't clear yet. It's a small purchase, but not a small decision, so here is an honest read on who it's for.

  • Product Inception makes sense if

    You're planning a serious software product, platform, or IoT product. It isn't clear yet what the first version should be or how to build it.

  • It doesn't if

    You need a brochure site or commodity CMS and plugin cleanup. You're shopping low-budget marketing work or comparing hourly rates. Or, you already know what to build. If that's the case you can skip this and go straight to the build.

Not sure it clears the bar? That's what the fit call is for.Request a fit call

the investment

Pay for the decision before the build

Product Inception settles the build decision before you spend on the build itself. The floor covers a focused one-week pass on one key question, and larger products cost more. You spend $10,000 now to avoid a six figure mistake later.

one to three weeks

Starting at $10,000

What moves the number

The more complex a project is, the more expensive it will be. Integrations, security compliance and hardware requirements are a few examples. We agree on the scope and the fee before we start.