Software House

A Software House That Builds It, Then Stays.

We are a founder-led software house building websites, online stores and custom platforms for businesses that need them to work. The people who scope your project are the people accountable for delivering it, and we are still reachable after it launches.

Why us

What you get to judge before you commit.

Hiring a software house means judging something you cannot inspect. You will not read the code and you will not sit in the stand-ups, so the honest questions are about how the work is run rather than how it is written. These are the four we think you should ask anyone, including us.

You deal with the people who build it.

We are founder-led. The person who scopes your project is accountable for delivering it, and you are not handed to an account manager once the contract is signed.

We scope before we quote.

A number produced before anyone understands the problem is a guess. We scope the build first, in writing, and the figure comes from that.

We are still here after launch.

Launch is the middle of the project, not the end. Care and support are a stated choice, and you keep a named contact rather than a ticket queue.

You own everything at the end.

Your domain, hosting and logins are in your name from day one. Source code and database are yours on final payment, with documentation. No lock-ins, and nothing is registered in our name.

What we do

What we build, and what we will tell you not to.

Most engagements start with one of these. If what you need sits next to them, ask: the full list is on our services page, and a project that is a poor fit gets referred out rather than taken.

Websites and web platforms.

Marketing sites, content-driven sites and landing pages, built so your team can edit them without coming back to us for a paragraph.

E-commerce.

Shopify and WooCommerce builds, migrations off a platform you have outgrown, and trade stores where pricing depends on who is logged in.

Custom software and web apps.

Portals, dashboards, booking systems and internal tools. Software that runs in a browser, scoped separately from a website.

Brand and identity.

Logo, visual system and the asset library that keeps it consistent once more than one person is using it.

SEO and content.

Technical foundations first, then the content that earns the rankings. A fast site with nothing worth reading does not rank.

Hosting, care and rescue.

Maintenance, security and speed work, and taking over builds left in a poor state. That one starts with an audit, not a quote.

How it runs

Four steps, and you always know which one you are in.

The rhythm is the same on every project. What changes is the depth of each step, not whether it happens.

01

Scope.

We work out what the build has to achieve before anyone opens a design tool. You get a written scope, and the things we have decided not to do are written down too.

02

Design.

You see real layouts with your own content in them, not a template with placeholder text. Revisions happen here, where they are cheap, rather than during the build.

03

Build.

Everything goes to a staging site first. You review it on a URL you can share internally, and nothing reaches your live domain until you have signed it off.

04

Launch and handover.

You receive the code, the accounts and written documentation. Ongoing care is a separate choice. How we run all four steps is on our process page.

Proof

Work we have actually delivered.

Independently owned since 2012, working with clients worldwide across finance, healthcare, public infrastructure and retail. See our portfolio, or ask us for the builds closest to what you are planning.

Common questions

The questions we are asked before we start.

The questions that come up most before a build starts.

What does a software project cost?

It depends on scope, and on how much is genuinely unknown at the start, which is why there is no list price here. A figure quoted before the problem is understood is a guess. We scope first, in writing, and the number comes from that.

A defined build has an end date agreed at scoping. What most often moves a timeline is not development but waiting for content and decisions, so we put dates on those too.

You do. Your domain, hosting and logins are in your name from day one, and the source code and database are yours on final payment, with documentation. Nothing is registered in our name, and there is no lock-in.

A named team, and you are told who before you commit. The person who scoped it stays accountable for it rather than handing you on.

Yes, and it starts with an audit rather than a quote. Inheriting a build made by someone else without reading it first is how a rescue becomes a second rescue.

Care and support are a separate, stated choice. You keep a named contact, and post-launch check-ins are part of the arrangement rather than something you have to chase.

Global Presence

Multiple continents, worldwide reach

14+ Years

Independently owned and operating

2,000+

Projects Delivered Worldwide

Tell us what you are trying to build.

Tell us what you are building and what it has to achieve. We will come back with an honest view of scope, including the parts we think you should not pay for yet.