Political campaign management software
The internal system a campaign office runs on: volunteers, booths, duties and field reporting in one place, designed for the person standing outside with a phone as much as for the person at the desk.
What this covers.
Every engagement is scoped in writing before it is built. These are the parts of it this discipline is responsible for.
Team and volunteer records
Who is active, in which area, reporting to whom, and what they are responsible for this week.
Booth and area structure
Booth, ward, block and constituency modelled the way the office is actually organised, rather than forced into a generic hierarchy.
Field reporting
Short structured reports submitted from a phone, so a day's activity reaches the office as data instead of as a thread of messages.
Scheduling and coordination
Events, duties and assignments held in one place, so the office rather than the group chat is the source of truth.
Roles and access control
Who can see and change what, set per role, with a record of changes on the data that matters.
Summaries and exports
Structured exports and summary views the office can take straight into its own meetings.
Built for a situation, not a side.
Campaign offices coordinating volunteers across more than one area.
Organisations whose field activity currently lives across spreadsheets and chat threads.
Teams that need one record of who did what, where, and when.
How it is built.
Phone first, desk second
The people entering data are standing outside on a mid-range phone. Every input is designed for that case first.
One typed data model
The structure is defined once, in types, so a report filed in the field and a figure read in the office cannot quietly diverge.
Permissions modelled on the office
Access follows the hierarchy the organisation already has, and changes to it are recorded rather than assumed.
Reporting built into the schema
Measurement is part of the data model from the start, not a layer bolted on when someone asks for a number.
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.
Coordination software, not a voter database
This system manages a campaign's own team and its own activity. We do not build voter rolls, voter scoring, household profiling or targeting lists into it, and we will not add them later.
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.