Submillis

Work

Systems businesses rely on.
Names stay confidential.

Every client I work with has signed an NDA, so I don't publish names, screenshots or case studies. What I can show you is what I build, how I build it and how I protect what you tell me.

Delivered for clients in

  • United Kingdom
  • Sweden
  • United States
  • Greece
  • Canada
  • Singapore
  • Finland
  • Nigeria
  • South Africa
  • Germany

Engineering capability

Proof of work, by depth.

This is the range of systems I design, build and maintain. Each area is work I have delivered for real businesses.

Business logic

The systems that run the back office.

ERP

  • inventory
  • procurement
  • purchasing
  • order management
  • multi-warehouse
  • production planning

Transactions

Software that handles money, orders and trust.

Marketplaces

  • multi-vendor catalogues
  • seller onboarding
  • commissions
  • payouts
  • disputes
  • reviews

Complex operations

Physical-world processes, modelled in software.

Logistics

  • shipment tracking
  • dispatch
  • route and load planning
  • carrier integrations
  • proof of delivery
  • fleet and driver management

Infrastructure

The foundations everything else stands on.

Identity and access (IAM)

  • single sign-on
  • OAuth 2 and OpenID Connect
  • role and permission models
  • multi-tenancy
  • MFA
  • session security

Modern engineering

Automation and intelligence, applied where it earns its place.

AI agents

  • task-focused agents that use your tools and data
  • guardrails
  • human approval steps
  • logging

Automation

  • replacing repetitive manual work
  • scheduled jobs

Product and delivery

The engineering around the code.

Web applications

  • responsive
  • accessible
  • fast
  • built with modern frameworks

Mobile

  • mobile-friendly and installable apps (PWA)

Architecture and technical audits

  • reviewing stuck, slow or fragile systems

A few familiar patterns

The situations where I'm usually called in.

No names, just the patterns.

Spreadsheets running the business

Critical processes live in files that break, get duplicated and depend on one person.

Systems that don't talk

Staff retype the same data across tools, and nobody trusts the numbers.

Growth outpaced the software

What worked at ten orders a day fails at a thousand.

An agency left a mess

Software that is slow, undocumented and impossible to change safely.

A launch with no owner

A product exists but nobody maintains, monitors or improves it.

Manual work eating the week

Approvals, reports and data entry that should run themselves.

Compliance and audit pressure

Teams need access control, trails and retention they can show.

A new idea needing a real build

A marketplace, platform or internal system that must be built properly the first time.

How I work

A process built for accountability.

The same steps on every engagement, whatever the size.

  1. 01

    Discovery call

    A direct conversation about your operation, the problem, who uses the system and what success looks like. I ask a lot of questions and challenge assumptions where it helps you.

    You get: a clear shared understanding, and an honest view on whether I'm the right fit.

  2. 02

    NDA and access

    Confidentiality is agreed before any sensitive detail is shared. Access to your systems is limited to what the work needs.

    You get: a signed NDA and a short access plan.

  3. 03

    Scope and plan

    I turn the problem into a written scope: what is built, what is not, in what order, with risks called out.

    You get: a scope document, milestones and a fixed price or clear estimate.

  4. 04

    Design and architecture

    Data model, system boundaries, integrations and security decisions are made on paper first, so the build doesn't wander.

    You get: a plain-language architecture summary you can review.

  5. 05

    Build in visible increments

    Work ships in small, working pieces you can see and test, not a big reveal at the end.

    You get: regular demos, a working preview environment and honest progress updates.

  6. 06

    Testing and hardening

    Automated tests, edge cases, security checks, performance checks and data validation before anything goes live.

    You get: a release checklist and confidence at launch.

  7. 07

    Launch and migration

    A planned release with backups, a rollback path and, where needed, careful migration from your old system or spreadsheets.

    You get: a calm go-live with no big-bang risk.

  8. 08

    Maintain and improve

    After launch I monitor, patch, support and keep improving what I built.

    You get: a named owner for your software, plus an optional ongoing retainer.

Confidential by default

Your business stays your business.

Because I work alone, your information doesn't pass through a team, a sales pipeline or an account manager.

NDA first

Signed before any sensitive detail is shared.

Least-privilege access

I request only the access the work requires and remove it when it ends.

No portfolio use

Your name, data, screens and code are never shown to anyone else.

Careful handling of data

Credentials in managed secrets, never in chats or code, and production data kept out of development wherever possible.

Clean handover

At the end, access, credentials and documentation are handed back to you.

One person

Fewer hands means fewer places your information can leak.

Need to talk through a specific security or compliance requirement? Raise it in the first call.

An honest answer

Fair question: how do you judge work you can't see?

  1. 01

    Ask me anything technical. I'll answer plainly, in the first call, for free.

  2. 02

    I'll walk you through how I'd build your system, before you commit.

  3. 03

    I can describe delivered work in anonymised, technical detail under your own NDA.

  4. 04

    Start small. A scoped first milestone lets you judge the work itself.

Questions

Before we talk.

Every client has signed an NDA and values privacy, so I don't publish names, screens or code. I show capability, process and approach instead, and I'm happy to discuss delivered work in anonymised technical terms.

Ready when you are

Tell me what you need to build.

NDA first, then the details. You'll hear back from me, not a sales team.

Start a project

See what I build