Election night ends one job and starts another. The field office becomes a district office, and the voters you contacted become constituents who call. We served that second job with a mode inside Romulus until it outgrew it.
Numa is our platform for sitting elected officials: one desk for the office your constituents call. It’s live at numa.northjerseyresearch.com.
Why a separate product
Campaign data lives under FEC and state campaign-finance law. Office data lives under public-records law (OPRA in New Jersey), with a strict no-electioneering line between them. That separation shouldn’t depend on discipline, so it’s built into the product: office records live in their own tables, with their own users and permissions, and a campaign login can’t open them. An incumbent running for re-election works in both, and each side sees only what its role allows.
What’s inside
- Casework: a constituent-services CRM with categories, assignment, and SLA tracking that flags a case before it breaches, not after.
- Constituents: the district’s people, their contact history, and every case they’ve ever filed.
- Legislative: bills, roll-call votes, and public Where-I-Stand pages.
- Communications: newsletters and press with per-recipient delivery tracking.
- District: demographics, service patterns, and annual report PDFs that show the district what its office did.
Constituents get a public portal where they can file a request and check its status through a private link, which means fewer “any update?” calls.
Meet Kennedy
Numa ships with Kennedy, the office AI. Ask him which categories are breaching SLA, who wrote in about the bus line, or what happened on a case last spring. He queries the live record, shows what he used, and respects permissions, so a staffer can’t get anything out of Kennedy they couldn’t see themselves. Nothing he drafts leaves the office without a person approving it.
If your office ran Romulus Office
Your cases, constituents, and records carry forward, and the Numa docs cover the new shape.