What we actually build

Nine project types, one delivery process. Much of the work is under NDA, so this page explains what we build and how - and we will show you relevant examples on a call.

Why no client logos

A straight answer about our portfolio

A large share of our work is internal business software, client portals and platforms covered by confidentiality agreements. Publishing screenshots of someone's ERP or patient records system is not something we are willing to do, and a wall of logos scraped together for decoration would not tell you much anyway.

What we can do is show you work directly relevant to your project on a call, including the parts that did not go to plan and what we changed as a result. That tends to be a more useful conversation than a gallery.

  • Relevant examples walked through on a screen-share
  • References from clients in a similar sector, where they agree
  • NDA signed first if you would rather talk in detail
  • Honest account of timelines and what they actually cost

How an engagement runs

Every project
1

Discovery: goals, constraints, and a written scope you sign off

2

Design: wireframes and interface concepts reviewed before any build

3

Build: fortnightly demos on a staging environment you can log into

4

Test: real devices, real data, and a parallel run for software

5

Launch: staged rollout with monitoring and a rollback path

6

Support: two weeks included, then an optional maintenance plan

Want to see work relevant to your project?

Much of what we build is internal software and client platforms we are not free to publish. Tell us what you are planning and we will walk you through comparable work on a call, under NDA where needed.