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.

Our story

Software people who learned the building.

If you have re-read a bill three times to find what changed, heard about an amendment later than you wanted, or sat in the chamber with your phone out waiting on a result, we have seen it. We have spent years in the Capitol watching good teams work that hard for information that should have come to them.

RTG's foundation is Cirkadia, a software studio with 30+ years of shipping production-grade software, layered with decades of Capitol expertise. RTG is road-tested through real California sessions and shaped by the teams who use it.

So we brought modern, lightweight engineering, and tools that are more timely and more collaborative, to the people who needed them most.
If you are a small shop, an association, a union or an advocate doing this work without a research department behind you, we built it for you.

Our data comes from sources we do not control, on the Legislature's schedule rather than ours. We get it right anyway, because if it is wrong or late, you are the one who walks into the client meeting with it.

What changes for you
Efficiency

Your morning starts with what moved.

Every bill, version and committee analysis, read and compared before you sit down, so you start with what matters instead of a stack to get through.

Discoverability

You hear it first.

RTG reads every amendment in the session, not just your list, so a bill you never tracked reaches you when it starts to matter.

Collaboration

Everyone knows who has what.

A name, a position and a note on every bill, with a nudge when something is due. One whip count your whole coalition shares.

One product, every shop. A two-person firm and a statewide association get the same whole thing. Nothing metered, nothing held back for a higher tier.

You don't have to take our word for it. Put RTG on your own bills for 14 days, and when you have a question, the answer comes from the people who build it.

Roll call

The crew. RTG never blinks.

The people who build RTG, run it, and answer when you write in. Every pipeline and process is monitored around the clock, in session or out, so RTG never blinks. A neural network only works if none of the nodes are asleep. The reading is automated. The judgment is not. Present and voting.

Joe Nachilo
Aye
Builds the product

Joe Nachilo

Architect

Builds systems that are not allowed to fail in public. For more than twenty years the consulting architect of the California Assembly's electronic floor voting system. Started in assembly code and COBOL; these days ships production features with coding agents between roll calls.

Aud Nachilo
Aye
Builds the product

Aud Nachilo

Crew lead, product

Thirty years of shipping production software. Designs and builds the AI agents and the product experiences that turn a firehose of bills, votes and committee activity into something a team can act on, working daily with coding agents across twenty years of living codebase.

Tio Satria
Aye
Builds the product

Tio Satria

Full-stack developer

Builds the parts you meet without noticing: the parsers, the background jobs, the plumbing that keeps the data honest. Ships while Sacramento sleeps, so the morning starts with new work already in place.

Rory Hinchey
Aye
Keeps it running

Rory Hinchey

Platform operations

The reason things still work at two in the morning, Pacific. Runs the daily checks on the pipeline overnight, so a California session opens with everything already in its place.

Matt Powers
Aye
Knows the building

Matt Powers

Advisor, Industry Relations

RTG's presence in the Capitol community, the person who walks into the room before we do. A name a lot of people in the building already know.

Kristine Joy Cabrales
Aye
Makes it click

Kristine Joy Cabrales

Onboarding, support & customer outreach

The one on the other end when you write in, from your first week through your second session. Learns how a shop actually works before showing it anything, and tends to check in before anyone has to ask. Carries whatever keeps coming up back to the people who build the product, which is how the product and the way we explain it both get better.

Ernesto Uribe
Aye
Opens the door

Ernesto Uribe

Field operations

Wiring up how RTG reaches the rest of California, and making sure we turn up speaking the language the work is already happening in. English + Spanish.

On the file
Works the halls

To be called

Next session

The chair is real and the nameplate is blank. If you know your way around the building and have wondered what it is like to work on the tool rather than just with it, say so before the file comes up.

In committee
Reads the room

Your name here

Next session

Still in committee, which in this building means the wording is not settled yet. If you read a room better than you read a job description, do not wait for the wording. Tell us what you would do with the seat.

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.