About

AI-forward, human-led.
Road-tested.
Built for California.

A team of software engineers building legislative intelligence the way Capitol clients said they needed it. One conversation at a time.

Who builds RTG

By people who understand software.

RTG's foundation is Cirkadia, a software studio with 30+ years of shipping production-grade software across legislative work, regulated industries, member organizations, and commercial products. RTG itself has been live for three-plus years, through real California sessions. Clean, cohesive, extensible, which sounds boring right up until you have to maintain a system that is none of those things.

That discipline is not decoration. RTG ingests bill text, amendments, committee analyses, vote records, and hearing calendars from sources we do not control, in formats that change without notice, on the Legislature's schedule rather than ours. People use that data to decide when to show up and what position to take. If the data is wrong or late, the mistake does not stay on a screen. It walks into a hearing room.

Layered with decades of Capitol expertise. Sharpened by the advocates, association leaders, and legislative practitioners whose feedback has shaped RTG across multiple California sessions.

The team is lean. Onboarding is run by the engineers who build the product. When something breaks, the fix comes from the same team. This is a feature, not a stage we're trying to grow out of.

None of which you have to take on faith. RTG is road-tested: it has run through real California sessions, on real deadlines, in the hands of teams doing the actual work. So we don't run a hard-push demo cycle. Book a walkthrough whenever you want one, and it will be with the engineers who built the product. Or skip it and start the trial: put RTG on your own bills, and judge it against the shape of your own work. The product makes the argument.

The cycle

Listen. Build. Ship. Return.

How a Capitol conversation becomes a feature, and how the next one starts. Between Listen and Build there is a mock: most features begin as a throwaway prototype built in hours, so an idea can be judged on a screen before any real code gets written.

How we build

Many features in RTG start as a conversation with a Capitol client. The roadmap walks in from the Capitol, not down from a strategy deck. Today's conversation shapes next week's release.

How we think

Six principles. Deliberate, not aspirational.

Stated here so you can hold us to them. These show up in product decisions, support behavior, and how we price.

01 · AI

AI-forward, human-led.

Most AI coding today is what people call vibe coding: you describe what you want, the AI writes it, and nobody reads the code. We use it for throwaway mockups. It is not how RTG is built. Inside the product, the engineer holds the shape and the AI does targeted work inside it. The same rule governs the AI you meet in RTG. It summarizes bills, flags position changes, and drafts first-pass briefs because an engineer decided exactly what job it does, what data it can see, and what happens when it is not sure. It doesn't replace the human judgment that moves whip counts.

02 · Built for California

California-deep, not California-shaped.

We chose to go a mile deep on one state rather than 50 states an inch thick. Every lobbyist, every CalAccess filer, every committee analysis, every floor vote. If you don't work California legislation, RTG isn't built for you, and we'll tell you so.

03 · Your shop

One product, every shop.

Rename the fields the way your organization talks. Switch off the features you never touch and they are gone for everyone, not greyed out. An association, a contract shop and a solo lobbyist all run the same RTG, and none of them see the same screen. The interface gets out of your way because you decided what was on it.

04 · Support

Engineer-led, not handed off.

When something breaks, you're talking to the people who built it. Onboarding sessions are run by the engineers. The phone is one number, one team.

05 · Roadmap

No black box.

Every RTG customer sees the roadmap from inside the product: what's in development, what's shipping next, what's parked, and why. Ideas don't vanish into a suggestion box. You bubble one up with a click, and the ones that ship turn up in “Bubbles that made it”. The roadmap we work from is the roadmap you see.

06 · Shipped

We ship it before we sell it.

The capabilities on this site are live in the product today. Three-plus years and multiple California sessions have road-tested them, in the hands of teams working real deadlines. Where something is still in build we say so plainly, and you can watch it move on the roadmap. A product that leans on an AI promise has to clear a higher bar than a good demo: whether the people behind it know their system, have run their system, and trust it to deliver. What we don't do is sell you a roadmap and call it a product.

On AI

It is not the AI on its own, and it is not us on our own. It is the symbiosis: an engineer who knows exactly what to ask for, working with a tool powerful enough to deliver it.

Contact

Talk to us.

One small team. Real human on the other end. Three ways to get started.

60-min walkthrough

One-on-one with the engineers who built it. No salesy script.

Book a walkthrough →

Support

Existing customers reach the same team that ships features.

support@realtimegov.com

Try RTG free for 14 days.

No credit card. Real California bills. Real votes. Full RTG, unlocked, for two weeks.

One phone line (916) 241-3436 · Sacramento
60-min walkthrough With the engineers who built it
Customer-referred Most new customers come from another customer.