Romain TordoRomain Tordo

Business application development

Internal systems and software for organisations whose operations do not fit productised templates. The work is architecture-first, delivery-disciplined, and explicit about ownership when the engagement ends.

Modern glass towers in a financial district, viewed from below

When off-the-shelf tools fail

  • Your workflow has exception paths and regulatory gates that products treat as edge cases.
  • You need one operational source of truth, not five systems bridged by spreadsheets.
  • Field, factory, or branch reality (connectivity, devices, shifts) breaks generic mobile modules.
  • Reporting must reflect how you measure the business—not only how a vendor models a “standard” industry.

When custom internal systems are justified

Custom work is justified when the cost of compromise (rework, manual reconciliation, operational risk, or audit exposure) exceeds the cost of building and maintaining a focused internal platform. That judgment should be explicit—scoped releases, measurable milestones, and a plan for run-state ownership—not an open-ended build.

Environments this fits

  • Industrial and manufacturing operators with shop-floor and back-office coupling.
  • Regulated operations (healthcare logistics, financial reporting workflows) needing traceability.
  • Multi-site hospitality, retail, and services groups with local variation under one model.
  • Infrastructure-heavy programmes where applications must sit on a coherent technical baseline.

Scoping and architecture discipline

  • Domain model and permissions before screen mock-ups: who acts, on what, under which rules.
  • Vertical slices into production rather than big-bang cutovers, unless constraints truly require them.
  • Integration boundaries are versioned APIs or batch contracts with monitoring—not hidden shared databases.
  • Security, backups, and recovery are designed in, with exercises that prove they work.
  • Handover artefacts your team can run: runbooks, ownership map, and escalation paths.

Selected implementations

Proof sits here—not in the capability cards above. Representative engagements where custom systems, ERP-style platforms, or large-scale integration work matched operational reality.

If your operations need software that matches the messy middle—not the demo script

Send context, constraints, and the outcome you need. I will respond with fit, risks, and a sensible engagement shape.