Skip to content

f12 build

Software that fits your business.
Not the other way round.

You know what your business needs software to do. We design, build and run it, so you can get back to running the business. Websites, applications, data systems, reporting. Experienced enterprise-grade engineers. Google Cloud specialists.


how we work

Three things F12 does differently.

01

Understand your business first, then build

No copy-paste quotes. Every project starts with a proper conversation about what your business actually does and what’s slowing it down. The software comes second, and it fits, because we took the time to get it right.
02

The whole picture, not just the code

Most developers build the thing you asked for. F12 thinks about how it all connects: the site people find you on, the system that takes their booking, the numbers that tell you if it’s working. One plan, everything joined up.
03

Fixed price or day rate. Your call.

Fixed price when scope is clear. Day rate when it isn’t. Either way, agreed up front in writing before we start. Any size of project welcome, from a single day’s work to a full build.

specialism

F12 is a Google Cloud specialist: architecture, deployment, running-cost optimisation, day-two operations. If your software runs on GCP (or should), that’s home turf.

process

How a project runs, start to finish.

  1. 01

    Scope it out

    A proper conversation about the business and the problem. What’s slowing you down, who it affects, what a good outcome looks like. An honest view on whether custom software is the right answer.

  2. 02

    Gather requirements

    A written brief we agree together. What the software must do, who uses it, what it needs to talk to, what “done” means. Price and timeline attached, agreed in writing before we start.

  3. 03

    Build the solution

    Weekly progress you can see and use. Short feedback loops so mistakes get caught early, not at launch. No six-month silence.

  4. 04

    Test & ship

    Every requirement tested against a real workflow, not a checklist. Bugs fixed, edge cases handled, then a proper launch with handover docs. Ongoing support optional, never required.

questions

The things people ask before they get in touch.

How does F12 price a project?
Two options, and you choose. Fixed price when we can scope the work cleanly up front, the number is written down and doesn’t move unless you change the scope. Day rate when the shape of the work is still emerging, useful for exploration, prototyping, or a support engagement without a defined end. Either way, agreed in writing before we start. Any size of project welcome, from a single day’s work to £15k+ builds.
How long does a typical project take?
A website is typically 2–6 weeks. A custom application is typically 4–12 weeks, but larger or more complex apps can run significantly longer, agreed after a complexity assessment. Data systems and reporting sit in between. We agree the launch date after scope and requirements are locked in, and it’s a date, not a hope.
What happens after launch?
You own everything: code, hosting, domain, accounts. We can walk away and hand it over, or stay on as an ongoing partner via a monthly retainer or per-ticket support. Either way, no lock-in.
What if the project turns out to be smaller than expected?
We’ll say so. If we scope a project together and realise partway through that a cheaper tool or a simpler approach would solve the problem, we tell you. Doing the right thing is worth more than billing the extra hours.
Do you work with software you didn’t build?
Sometimes, case-by-case. If a previous developer left something half-finished, or an inherited system needs a fresh set of eyes, we’ll take a look. Not every project is a fit, but many are.
Why Google Cloud specifically?
Because we’ve spent years going deep on it. Google Cloud tends to give small businesses a better cost profile than the alternatives, and its managed services mean less to break. We’ll happily work on other clouds when a project calls for it, but GCP is home turf.

next step

Tell us what you’re trying to do.

A quick chat about your objectives. No slides, no pitch, just a proper conversation. If we’re a fit we’ll say so; if we’re not, we’ll say that too.