How we build
Melosome develops ventures through a controlled progression from understanding to stewardship.
We do not treat every idea as a company, every prototype as a product or every deployment as proof of value. Each stage must earn the next.
1. Understand
We define the problem in its real environment.
That includes the people affected, existing processes, rights and responsibilities, commercial conditions, regulatory constraints, security risks and the consequences of failure.
The objective is not to produce a larger requirements document. It is to establish whether the problem is meaningful, whether technology is an appropriate response and what success would actually look like.
2. Research
We investigate the domain, available evidence, technical approaches and unresolved questions.
Research may include:
- user and stakeholder discovery;
- market and operational analysis;
- technical experiments;
- threat modelling;
- policy and regulatory analysis;
- data assessment;
- prototype evaluation; and
- examination of whether a simpler non-technical answer exists.
Research is time-bound. It must lead to a decision, not become a permanent substitute for delivery.
3. Design
We design the service, product, operating model and technology as a coherent system.
This stage establishes:
- the value proposition;
- the user journeys;
- responsibilities and controls;
- data boundaries;
- security and privacy requirements;
- architecture;
- evidence and audit needs;
- delivery constraints; and
- the smallest useful release.
Design does not eliminate uncertainty. It makes the important uncertainty visible.
4. Build
Engineering begins with the smallest end-to-end capability that proves the product can work.
We favour:
- working outcomes over infrastructure theatre;
- simple, replaceable components;
- automation where it reduces repeatable risk;
- clear boundaries;
- testable behaviour;
- secure defaults;
- observable systems; and
- delivery plans created with the engineers doing the work.
5. Validate
A product is tested against real use, not only internal expectations.
We look for evidence that:
- the problem is being reduced;
- users understand and trust the product;
- risks remain controlled;
- the operating model is sustainable;
- the technology can be maintained; and
- continued investment is justified.
6. Steward
Launch is the beginning of responsibility.
Stewardship includes maintaining quality, responding to security issues, protecting rights, improving accessibility, preserving evidence, managing change and deciding when a system should be simplified, replaced or retired.
Portfolio stages
Melosome describes work using three broad states:
Research
The need and possible response are being investigated. Public detail is limited.
Build
A validated concept is being engineered into a usable product. Disclosure remains controlled.
Steward
The product has active users, customers or partners and is supported as an enduring venture.
What we do not publish
We do not publish:
- speculative launch dates;
- unreleased product roadmaps;
- internal architecture diagrams;
- confidential partner discussions;
- detailed security controls;
- unvalidated performance claims; or
- lists of ideas presented as operating businesses.
We believe restraint protects the work and makes public statements more meaningful.
Working with Melosome
We consider conversations where there is a clear problem, credible commitment and alignment with our principles.