01

Enterprise software products

Software from Recurring Enterprise Problems.

Our products are developed from problems we see again and again across complex enterprise environments. We focus on the space where standard platforms stop and customer-specific architecture begins.

02

Where products come from

Engagements Find the Problem. Engineering Solves It. Software Repeats It.

  1. Architecture engagements reveal a recurring problem

    The same gap appears across different landscapes, platforms and industries.

  2. Engineering solves it in a real landscape

    Under the same controls as any delivery: contracts, deterministic numbers, verification.

  3. Repeatable patterns become products

    Configurable, tested and supported software, with its status stated plainly.

03

Product

Value Lens Private beta

Decision support and financial controls over ERP data.

Value Lens reads commercial and cost facts through read-only tools, computes results in deterministic code under versioned policies, and raises evidence-backed cases that a reviewer accepts or dismisses with a reason. Its first use case is margin leakage in order-to-cash: where an enterprise lost money it should not have lost, and why.

  • Read-only by designValue Lens never writes to source systems.

  • Deterministic numbersCalculations in exact integer arithmetic under a versioned policy.

  • Evidence per caseSources, calculation and decision kept together.

  • People decideAgents explain; a reviewer accepts or dismisses.

Private beta on synthetic ERP-like data. Production ERP connector in development.

04

Problem areas

Where We Are Working Next.

These are recurring problems from our engagements, not products. When one becomes a product, it will appear here with its status stated plainly.

01

Operational Intelligence

Decisions that depend on data from several systems, assembled by hand every week.

02

Risk and Controls

Controls that are documented but not continuously evidenced across systems.

03

Integration Governance

Interfaces without a single register of owner, contract and health.

04

Cross-System Reconciliation

Totals that should agree across ERP, data platforms and partners, and do not.

05

Architecture Intelligence

Landscapes whose current state is known only to the people who built them.

06

Agent Execution Control

AI actions that need validation, approval and verification outside any one vendor.

05

Next step

Have a Recurring Problem the Platforms Do Not Solve?

Tell us about it. If it repeats across landscapes, it may be the next thing we build.

A conversation with an architect, not a salesperson. Replies within one business day. NDA before discovery.