Brand narrative and identity
What the product is for, who it is for and what it has to prove before anyone believes it. Positioning, naming and the identity that follows. Scope gets cut here rather than three weeks before launch.
We work with founders who have an idea and need it to become a human centric product. Strategy, design, engineering and the launch itself, all under one roof.
Your customers have learned to spot generated design and generated writing within about two seconds. Once they spot it they stop reading and everything you spent on the page is spent for nothing.
That recognition also works in your favour. A product that shows evidence of decisions, of somebody choosing this word and this measure of space, holds attention long enough to be understood.
Every page we ship is drawn by people who can tell you why each part of it looks the way it does. This one included.
Four kinds of work. Most projects use two or three of them and we would rather tell you which ones you do not need.
What the product is for, who it is for and what it has to prove before anyone believes it. Positioning, naming and the identity that follows. Scope gets cut here rather than three weeks before launch.
Interface and interaction drawn for your material rather than assembled from a template. You get a design system your own team can extend, with the reasoning written down beside it.
Ingestion, database, API and front end, built and deployed and handed over with documentation. We work in your stack where you already have one and pick a boring one where you do not.
The narrative, the content system that carries it and the weeks after release when the product either finds its audience or does not. We stay through that part.
The same four stages every time, so you always know which one you are in and what comes out of it.
We read what you already have, talk to the people who use it and write back what we would build, what we would leave out and what it costs.
Identity and interface, drawn and reviewed in the open. You see the work weekly rather than a deck about the work.
A fixed scope shipped in reviewable increments, on your infrastructure or ours, with tests and documentation as part of the scope.
Release, the narrative around it and the handover. Either your team takes it with a walkthrough, or we stay on a set number of days a month.
The people you meet in Define are the people writing the code in Develop. Nothing is passed down a chain.
We build our own software on the same pipeline we build for clients. That is how we know it holds.
Exports, spreadsheets, APIs and scraped pages land in one store, normalised, with a record of where every row came from.
Run analyses on your data and get answers as charts and reports. When a question is ambiguous it asks; when the data cannot answer it says so.
Pin an answer to a shared dashboard and it refreshes on its own, so the decision it supports stays based on today's data.
Invertropy runs all three steps as one product, and our client work is built on the same three steps
Turn your data into business decisions. Invertropy brings your data together, runs the analyses you ask for as charts and reports, and keeps the answers you rely on current on a shared dashboard. It also embeds in a product you already have.
A publication on what actually works in global development, with real indicators and cited sources. It runs on Invertropy, which makes it the honest test of whether Invertropy is any good.
Send the shape of the problem, whatever you already have and when you need it working. We read everything and reply within two working days.
If we are a good fit, the next step is a short intro call rather than a proposal document.
Start a project