Supervention
Send your requirement
Choices we make for you

We choose the tools. You keep the keys.

A wall of logos tells you nothing about your project. So this page lists our choices by job: where your software runs, where your records live, how it talks to WhatsApp, how we test, how we watch it, how your code is kept safe. For each job you see our pick, why we pick it, and what we would pick if your case were different.

Named in your proposalEach card names the kind of tool we reach for. The exact tool depends on your project, and your written proposal names it. The reasons are how we decide, and they stay the same.

Set your caseHow we choose

Flip a switch. Eight choices think again.

Each card below is one job. It shows the pick we start from. Tell us three things about your case and every card chooses again. The cards that changed are marked, and the old pick stays on the card so you can see what moved.

Default picks

These are our default picks. Flip a switch above and watch the cards choose again.

What it is written in

What are the screens, and the logic behind them, built with?

Default pick
Our pickNamed in your proposal

Widely used, well-known technology for the screens and for the logic

Why, in plain words

Both are widely used, so many developers already know them. If you ever part ways with us, another team can take over without learning something rare.

What we pick instead, when your case differs
  • Small budgetA ready-made app builder for the simple parts, with code only where it is needed
  • Many users at onceSame pick. These tools scale well. If one part gets busy later, we split that part out and say so in writing.
  • Data must stay in one countrySame pick. A programming language does not decide where your data sits.
More on this: Software development
What you own. The code sits in a repository in your name, and the documents come with it.

Where it runs

Which computers does your software run on?

Default pick
Our pickNamed in your proposal

A large cloud provider, in an account that is yours

Why, in plain words

A large cloud is the safe default. It is widely understood, easy to hand to another team, and it can grow when you need it to. We choose the region with you.

What we pick instead, when your case differs
  • Small budgetOne small shared server from a hosting company
  • Many users at onceA large cloud provider with automatic scaling and a load balancer
  • Data must stay in one countryA large cloud provider, in a data-centre region in the country you name
More on this: Cloud setup and migration
What you own. The cloud account is opened in your name. We are added as users, and you can remove us. The code and the setup notes are yours too.

Where your records live

Where are your customers, orders and files kept?

Default pick
Our pickNamed in your proposal

A well-known database

Why, in plain words

A database that many teams know. It keeps your records tidy and stays correct when two people change the same thing at once. Backups are set up together with the rest of the system.

What we pick instead, when your case differs
  • Small budgetSame pick. On a small budget it shares the small server, so there is nothing extra to run.
  • Many users at onceA well-known database with a read copy and a cache
  • Data must stay in one countryA well-known database in a region in the country you name, with backups kept there
More on this: Data and analytics
What you own. The database is in your account and the records are yours. You can ask for a full copy at any time.

How it talks to WhatsApp and phones

How do messages and calls reach your customers?

Default pick
Our pickNamed in your proposal

The official WhatsApp business route through an approved provider, plus a calling and SMS provider

Why, in plain words

We use the official route, because shortcuts can get a business number blocked. Your number and your message templates stay in your own business account.

What we pick instead, when your case differs
  • Small budgetA click-to-chat button and email alerts, with no automatic sending yet
  • Many users at onceThe official WhatsApp business route with a message queue for rushes
  • Data must stay in one countryA messaging provider with servers in the country you name, where one is available
More on this: Intelligent automation
What you own. The business number, the messaging account and the templates are in your name. AI, WhatsApp and calling usage is billed at cost and shown in the monthly report.

Which AI answers

If your software uses AI, which model does the thinking?

Default pick
Our pickNamed in your proposal

A hosted AI model from a major provider, kept swappable

Why, in plain words

We pick the model that does your job reliably, test it on your own examples, and keep it swappable so a better one can replace it later. Every AI agent has rules for handing over to a person.

What we pick instead, when your case differs
  • Small budgetA smaller AI model for the simple, repeated questions
  • Many users at onceA hosted AI model from a major provider, with cached answers and a second model as back-up
  • Data must stay in one countryAn AI model hosted in the country you name, or one that runs on your own server
More on this: AI agents
What you own. The accounts that call the AI are in your name, and so are the prompts and rules we write. Whether your data may be used to improve a model is agreed in writing before we start.

How we test

How do we know it works before you do?

Default pick
Our pickNamed in your proposal

Automated checks on every change, then a person tries the release

Why, in plain words

A machine repeats the dull checks the same way every time. A person then tries the things a machine would not think of. Every system ships with tests and human checks.

What we pick instead, when your case differs
  • Small budgetA short set of automated checks for the three paths that would hurt most, plus a person’s test
  • Many users at onceAutomated checks, plus load tests
  • Data must stay in one countrySame pick. Test records are made up, not copies of your real customers, unless we agree otherwise in writing.
More on this: Software testing
What you own. The tests are part of the code you receive, so any team can run them.

How we watch it after launch

Who notices when something breaks, and how fast?

Default pick
Our pickNamed in your proposal

An error tracker, an uptime check and a dashboard

Why, in plain words

We want to know about a problem before you do. Errors, slow pages and downtime each raise a flag, and a person looks at it. An uptime check simply asks your site, again and again, “are you there?” Every system ships with monitoring.

What we pick instead, when your case differs
  • Small budgetA free uptime check and an error email
  • Many users at onceAn error tracker, an uptime check and a dashboard, with alerts on speed and load
  • Data must stay in one countryAn error tracker, an uptime check and a dashboard, hosted in the country you name, with personal details removed from error reports
More on this: Managed hosting
What you own. The monitoring accounts are in your name, and the dashboard is yours to open at any time.

How your code is kept safe

Where does the code live, and how do you get it all at the end?

Default pick
Our pickNamed in your proposal

Your code in a repository in your own organisation, with a password vault for secrets

Why, in plain words

The code sits in an account that is yours from day one. We are guests, with access you can take away. Passwords and keys live in the vault, never inside the code.

What we pick instead, when your case differs
  • Small budgetSame pick. A free plan is enough to start, and you upgrade in place later.
  • Many users at onceSame pick. What changes with many users is how strict the checks are before a release, and that is covered under testing.
  • Data must stay in one countryA code server in the country you name, in your name, with the password vault there too
More on this: What you own at the finish line
What you own. You own the code, the accounts and the documentation. At the finish line you receive all three.
Your kit on one page

Your case, as a list you can hand to anyone.

Take it to another agency or a freelancer and ask: is this what you would use, and if not, why? A good answer is a reason. A logo is not a reason.

Send it to us

Case: default, no switch setNamed in your proposal
  1. 1. What it is written inWidely used, well-known technology for the screens and for the logic
  2. 2. Where it runsA large cloud provider, in an account that is yours
  3. 3. Where your records liveA well-known database
  4. 4. How it talks to WhatsApp and phonesThe official WhatsApp business route through an approved provider, plus a calling and SMS provider
  5. 5. Which AI answersA hosted AI model from a major provider, kept swappable
  6. 6. How we testAutomated checks on every change, then a person tries the release
  7. 7. How we watch it after launchAn error tracker, an uptime check and a dashboard
  8. 8. How your code is kept safeYour code in a repository in your own organisation, with a password vault for secrets

In every case, the accounts, the code and the documents are in your name.

How we choose

Three tests before any tool goes on your list.

We do not fall in love with tools. Any tool we add to a project has to pass all three, and we apply the same tests to the ones you or other people suggest.

  1. You can leave it.

    Could another team take over in a short time? The account is in your name, your records can be exported and the code sits in a place you own. A tool that locks your data in a form only it can read fails this test.

  2. It has a support path.

    When it breaks, someone has an answer: a company with a support desk, or a large community that has met the problem before. A tool that one person built and nobody looks after fails this test.

  3. We can explain it in one sentence.

    If we cannot say in plain words what a tool does for you, it does not go in your project. A tool nobody can explain is a risk you would be paying for.

Got a tool someone else suggested?

Try it yourself

Type its name if you like, then tick each test it passes. You get a plain verdict and the question to ask next.

This tool: 0 of 3

Not yet.

This tool has passed none of the tests so far. Ask the three questions above before you agree to it.

Asking about a tool we did not list?

The questions page answers the technology question in plain words, and it has a box for the one nobody has asked yet. The tools for your own project are agreed in writing before we start.

Where your data goesWhat moves the priceSample documents

Read the technology questionDiscuss your project