Skip to main content

How I operate

Commitments that survive contact with reality.

One architect, one accountable line. The sequence below is how every NEXUZ engagement runs, from the first call to the moment the keys change hands.

  1. 01

    Discovery

    A working session on the process itself — who touches it, where it breaks, what it costs today. The output is a written problem statement we both agree on.

    What you bringAccess to the people who actually do the work.

  2. 02

    Architecture

    A concrete design: data model, access rules, integrations and money paths — including what is deliberately left out. Costed, with running costs stated up front.

    What you bringA decision. Approve, adjust, or walk away with the architecture.

  3. 03

    Build

    Working software in front of you throughout, in short cycles. No reveal at the end, no invoice for a surprise.

    What you bringRoughly an hour a week to review and steer.

  4. 04

    Handover

    Repositories, infrastructure, migrations, credentials and documentation transferred into your accounts, with a walkthrough for whoever will own it.

    What you bringA named owner internally, even if that person is you.

Commitments

Three things that do not change, whatever the project.

  • You own everything at the end

    Code, infrastructure, data and documentation are transferred to you. Nothing is held back as leverage.

  • Compliance enforced by code

    Access rules, encrypted personal data, tamper-evident history and automated checks — applied to every build, not just the regulated ones. The controls live in the software, not in a policy document.

  • Carbon removal on every project

    A share of every engagement funds verified carbon removal. It is costed in from the start, not offered as an upsell.

Plain speaking

What you will be told, whether or not it wins the work.

  • If an off-the-shelf tool or a spreadsheet would genuinely serve you better, you will be told that on the first call.
  • If a project needs a team rather than one architect, that is said before a proposal is written.
  • Where I take a share of revenue, that is stated up front and written into the agreement.
  • Estimates are fixed once scope is agreed. Changes are re-quoted rather than absorbed quietly.
  • Outcomes on this site stay qualitative unless a client has verified the numbers.

Smaller scope than a platform? NEXUZ Lite is the lower-commitment way in.

Next step

Tell me what the business runs on today.

No pitch deck, no discovery fee. If something off the shelf would genuinely serve you better, I will say so before either of us spends money.

Prefer to write it down? Send a full enquiry with what you are trying to build.