Skip to content
Back

Embedded · Make-or-buy

Which building block is up for decision?

Enter your question and the building block. You get a record whose status is computed from its fields — and beside it, the list of what is still missing before the next stage.

A question, not a heading. “Do we build the communication stack ourselves?” is one; “Communication stack” is not.

Load a record from a file

An exported record or a candidate from the Make-or-buy Kit. JSON either way.

This record is stored on my server, reachable only through the link that will then be in your address bar. I do not see it in any overview. After 90 days without a change it deletes itself; with “Delete record” immediately.

If you only need one thing

Three results that stand on their own

  • Delivery delta report

    You bring
    Two ARXML delivery states.
    You get
    A delta: schema revisions, occupied layers, communication surface, variants — with the source files behind every number. Without a shared anchor it refuses to compute the delta rather than subtract two unrelated sums.
  • Make-or-buy kit

    You bring
    Seven facts about your programme.
    You get
    A direction per building block, the criterion that decided it, and the decision right. As text and as JSON.
  • AI deployment order

    You bring
    A description of your work areas.
    You get
    Four zones for agents, a one-pager for management, and a permissions file that sits next to an agent configuration.

Scope

What is not included

I build no base-software stack and compete with no vendor — I make the decision between them defensible. Approvals and standards testing sit with the test bodies and your specialists; I name no standard I cannot evidence. Hardware development stays with your engineers. Changes of scope are discussed beforehand.

Tell me what is up for decision.

Twenty minutes are enough to find out whether it fits: which building blocks, how many variants, and what has to be evidenced first.

Book an introductory call (20 min)