Custom political technology
When the requirement has no product to buy, we design and build it: internal tools, data systems and interfaces shaped around one organisation's way of working rather than around a category.
What this covers.
Every engagement is scoped in writing before it is built. These are the parts of it this discipline is responsible for.
Discovery and scoping
What the work actually is today, where it breaks, and the smallest system that would change that. Written down before anything is built.
Data modelling
The organisation's own entities and the relationships between them, settled before an interface is drawn over them.
Internal tools and dashboards
Interfaces for the people inside the organisation, built for the task they do all day rather than for a demonstration.
Integration
Connecting what is already in use, so the new tool does not become one more island with its own copy of the truth.
Migration
Moving what exists — spreadsheets, documents, exports — into the structure, with the originals kept intact.
Documentation and handover
Written so the next person can run it, including the next person who is not us.
Built for a situation, not a side.
Organisations with a process that no off-the-shelf product matches.
Teams running something critical in a spreadsheet that has long outgrown it.
Offices that need a tool built around how they already work, not a workflow rebuilt around a tool.
How it is built.
Scope before code
A written scope with the data model in it. What we are not building is listed as explicitly as what we are.
Small, verifiable steps
Shipped in increments that can be used and judged, rather than in one delivery at the end that nobody has seen.
Typed end to end
One set of types from the data store to the interface, so a change that breaks something fails at build time instead of in use.
Built to be handed over
Readable code, recorded decisions and access that belongs to the organisation from the start.
Categories of tooling, not credentials. The final choice is made per project and recorded in the scope.
What we will not build.
We build infrastructure for political work. That is not the same as building machinery for political manipulation, and the difference is written down rather than assumed.
Some systems we will not build
A custom brief is still a bounded one. We decline work whose purpose is voter profiling, micro-targeted persuasion, synthetic or impersonated content, surveillance of individuals, or circumventing a platform's rules — whatever it is called in the specification.
Consent first
Outreach runs on contacts who have opted in, through each channel's own approved mechanism, with an opt-out that works. We do not build around a platform's consent rules.
No profiling, no persuasion engineering
We do not build voter scoring, psychographic profiling, micro-targeted persuasion, or any system whose purpose is to change how a person votes without their knowing why they are being shown it.
A person in the loop
Anything an AI system produces for an audience outside the organisation is reviewed by a person before it is published or sent. That review is part of the software, not a rule somebody has to remember.
Nothing invented
No claim, figure, endorsement or credential goes live unless the organisation can evidence it. The rule applies to this website as strictly as it applies to yours.
Tell us what it has to do.
Describe what you are running and what this has to handle. We will tell you what we would build, what it would take, and what we would leave out.
Rajasthan first, India next.