Experiment2026
Freshly Support Lab
An independent technical demonstration of merchant support investigation: deterministic diagnostics, sourced knowledge, and an evidence-based escalation path.
- Product engineering
- Diagnostic engine
- Grounded AI
Independent technology company
You describe.We build.
Your ideas are valid. Let’s bring them to life. Software, enterprise systems, infrastructure, security and automation — designed, built and handed over by the person accountable for it.
PossibilityArchitecture
01Philosophy
Mediocrity is not a skill gap.It is a refusal to figure it out.
Most systems do not fail because the problem was unsolvable. They fail because whoever was responsible stopped at “I haven’t worked with this before.” The domain changes. The standard does not.
Networking, cloud, systems administration, virtualisation, security. Walk into something unfamiliar, take it apart, and leave it more reliable than you found it. That is the whole discipline.
The position
Reject mediocrity. Challenge limitations.
- N
- No. Not possible. Not our problem.
- A
- A new direction. The same letter, struck through.
The strike begins at the beginning — the start of change, not the end of a word.
02Capabilities
Six layers of one system.
Most engagements use more than one. A product needs a platform; a platform needs a network; a network needs a security posture. We work across the stack, not inside a single box.
Product engineering from first sketch to production: interfaces, services, data and the operational discipline around them.
Read the capabilityERP, commerce and business platforms wired together properly — with clean data contracts instead of brittle point-to-point glue.
Read the capabilityNetworks, servers and platforms designed for the failure cases, not just the happy path — documented, monitored and reproducible.
Read the capabilityPractical hardening and defensible architecture: least privilege, segmentation, evidence, and recovery that has actually been rehearsed.
Read the capabilityRepetitive work moved into systems that can be audited — deterministic where it must be, intelligent where it genuinely helps.
Read the capabilityClear technical judgement on decisions that are expensive to reverse: architecture, platform choice, delivery risk and sequencing.
Read the capability
Layer 01 / 06
Detail → Open
03Approach
How an idea becomes
a system you can own.
Six stages, each with an artefact you keep. The sequence is deliberate: the decisions that are expensive to reverse are made before they are expensive.
Not every engagement runs the full sequence. Every engagement ends with something you can operate without us.
01
Understand
The problem as it actually is.
We start with the operation, not the software. What happens today, who does it, where it breaks, what the constraint really is. The brief is usually one layer above the actual problem.
- Constraint map
- Current-state notes
- Success criteria
02
Architect
Decisions before code.
Boundaries, data ownership, failure modes, and the trade-offs we are accepting. Written down, so it can be challenged now rather than discovered in production.
- Architecture decision records
- Data model
- Risk register
03
Build
Small, verified increments.
Working software in reviewable slices. Typed boundaries, tests around the behaviour that matters, and nothing merged on the promise that it will be fixed later.
- Working increments
- Test coverage
- Design system
04
Integrate
Where most projects fail.
Real data, real permissions, real edge cases. Integrations are contracts with validation and idempotency — not scripts held together by hope.
- Integration contracts
- Migration and reconciliation
- Access model
05
Validate
Evidence, not assurances.
Load, failure, recovery and accessibility are tested rather than assumed. If a claim matters, there is a check that proves it.
- Verification report
- Recovery rehearsal
- Accessibility audit
06
Evolve
Built to be changed.
Documentation, observability and a handover that leaves you able to operate and extend the system without us. Ownership is the deliverable.
- Runbook
- Monitoring
- Handover
04Work
Built, tested,
and shown.
No client logos, no invented case studies, no revenue figures. What is here is real: experiments you can open, and systems running in production.
Experiment2026
This site
The experience you are in. A canvas-driven study of an idea resolving into an architecture, built without a 3D engine.
- Creative engineering
- Canvas
- Motion
You are looking at it
Client work is shared privately, with permission, during a conversation.
All work and experiments05Start
You describe.We build.
Tell us what you are trying to build, what is currently in the way, and what “working” would look like. You will get a straight answer about whether it is a fit — and who would do the work.
No discovery-call funnel. The first reply comes from the person who would be accountable for the outcome.
Independent · Founder-led · Accountable