Most offices run casework out of shared inboxes and spreadsheets nobody can search. Numa is one record: every case, every position, every reply.
Casework · Constituents · Legislative · Communications · District · Analytics · Operations
Kennedy · the office AI
Meet Kennedy. He keeps the record.
Kennedy lives in two places: his own workspace, and a concierge you can call up from any screen. Ask him which categories are breaching SLA, have him suggest categories for a morning's inbound mail, draft a reply in the office's voice, or summarize a six-month case thread before a constituent calls back.
He only drafts. His drafts wait in Comms for a staff member to finish, so nothing reaches a constituent unless a person sends it, and AI requests are logged.
Numa and Romulus
Same team. Separate records.
Numa and Romulus, our campaign platform, are built by the same team at North Jersey Research.
Office records live in their own tables, with their own users and permissions, and a campaign login can’t open them. Campaign history appears in a case only when the record is voter-linked, a role allows it, and the office has granted access. Every view is logged.
Setup
What changes in week one
We run onboarding. Your staff's part is about a week of short sessions.
-
Day 1
The office takes shape
We set up your districts, case categories, and response-time targets with you, and create staff accounts and roles.
-
Days 2 and 3
Your casework comes in
We bring in the cases you already have, from spreadsheets, inboxes, and your predecessor's files, and connect the office email address so new mail becomes cases.
-
Day 4
The legislative record
Current bills, committee seats, and any positions the official wants public from the start go in.
-
Day 5
Public pages, on purpose
You review the public pages and switch them on deliberately: Where-I-Stand and the events feed first, the constituent portal when the office is ready.
By the end of the week the queue is real: open cases with owners and response clocks, not an empty database.