§ 01

Moving to RTG

Three promises, whatever your starting point

However you start, help is one call away.

Three things we put on the table the day you sign up. None of them are sales-team policies that quietly disappear after onboarding.

Help when you want it. Skip it when you don't.

Engineer-led kickoff, sample import, workflow walkthrough — all included if you want them, all skippable if you don't. The 14-day trial is yours, used however suits you. The same engineer is on the phone if you change your mind midway.

Bring your sheet, leave your sheet.

Upload the tracking book you keep today, straight from your current tool's export. RTG matches the bill numbers, maps your columns and your vocabulary, and shows you exactly what will happen before anything is written. Positions, advisory positions, priorities, clients, tags, and who is assigned come across; anything RTG cannot place is set aside for you rather than guessed. Run it yourself, or hand it to an engineer.

Decision day at 14.

Monthly, annual, or walk away clean. No call-with-success-manager dance. If you cancel, your data is preserved for 30 days in case you change your mind — the decision is genuinely yours.

§ 02

The next 14 days

Trial-first · engineer-led · decision day at the end

What actually happens, day by day.

The 14-day trial is your runway. The timeline below shows the two paths — bringing data from another tool / spreadsheet, or starting clean. Either way, the decision day is day 14, not day 1.

Day 0

Kickoff · 60-min call (optional)

An RTG engineer walks you through the workspace and answers anything you want answered. No salesperson, no scripted demo. The person who builds it.

Bringing dataWe confirm which bills to import as a sample, what your team looks like, how you currently work.

Starting cleanSkip the call entirely if you want — we're on the phone the moment you need us.

Day 1

Your workspace is ready

By end of day one you're in RTG, looking at real California legislative data: live floor activity, the bill search, the dashboard.

Bringing dataDrop your export on the Connections page and run the import yourself, mapping your columns once. Preview first, write second. An engineer will do it for you if you would rather.

Starting cleanSign up, pick the bills that matter to you, track them with one click. We don't need to do anything for you to start.

Days 2–13

Use RTG on real California work

This is the trial in motion. Same engineer is your contact through the whole window — phone, email, whatever you prefer.

Bringing dataParallel run with your current tool. Week one includes a live workflow-alignment session — how Position Matrix replaces flipping between PDFs, how Votecards replaces the shared whip spreadsheet.

Starting cleanRTG points out each screen the first time you open it, and you can replay any of it from the Guide. Plus the search palette and the Pulse mobile app. Ask when you want to — we don't push.

Day 14

Decision day

Three honest options — same for everyone: walk away clean (workspace freezes, your data preserved for 30 days), continue monthly (carry on with what you've set up), or commit to annual (and if you're switching, the full portfolio import + 30-day guided onboarding kicks in). No call-with-success-manager dance.

Day 14, two paths

Continue monthly, or go all in.

Monthly

Continue with what you've imported.

Keep the sample bills you've been working with on the trial. Add more as you go — tracking new bills is a one-click action. Switch to annual any time and unlock the full portfolio import.

From $100 / user / mo
Same product, same features
Cancel anytime

Annual Recommended

Engineer imports your full portfolio.

Your full portfolio brought over from your current tool — positions, tags, priorities, attributed notes intact. 30-day guided onboarding window with the same engineer through the whole arc.

From $85 / user / mo · saves 15%
Full portfolio import included
Migration help across the first month

Both figures are the 1–4 seat rate. Volume pricing lowers the per-seat price at 5 seats and again at 10, automatically. See the full rate table →

§ 03

Built to be left

Lock-in is a competitor's problem

Data portability principles

If we don't earn it, we don't keep it.

The reason switching from another tool feels hard isn't because the work is complex. It's because the incumbents were designed to be sticky. CSV exports buried four menus deep. Position history attached to your account, not your data. Migration tools that don't exist.

We took the opposite stance: RTG is built to be left. Not because we want you to. Because a tool that can't be left is a tool you stop trusting.

01
Self-serve CSV export Run a full report from inside RTG and export every field flagged as exportable — tracked bills, positions, history, attributed notes. Everything you put in, you can take out.
02
30-day data preservation Cancel anytime — your workspace freezes immediately, but your data sticks around for 30 days in case you change your mind.
03
Month-to-month available No annual lock-in required. Annual saves 15%, but month-to-month is a real option, not a hidden one.

§ 04

Questions teams ask

From teams bringing data and teams starting clean

The questions teams actually ask.

Not theoretical concerns — real ones, from real conversations with teams moving to RTG from another tool, from a spreadsheet-and-email workflow, or from no tool at all.

Yes — that's the “starting clean” path. Sign up, pick the bills that matter to you, track them with one click. Every page has its own help link, the search palette is one keystroke (Ctrl+K), and you can call us at 916·241·3436 if you want to talk to an engineer.

You don't have to take a kickoff call, ask for a sample import, or schedule a walkthrough to use the trial. Help is always at hand — we just don't push it on you.

Yes — as long as your current tool lets you export it. An RTG engineer handles the import for you — you hand us the export from your current tool, we land it in RTG. Positions, tags, priorities, attributed notes all come over.

What doesn't come over cleanly: deeply customized tag taxonomies that don't have a 1:1 equivalent in RTG. We resolve those during the workflow-alignment session in week one so nothing gets lost in translation.

What we have today: every California bill from 2019 onwards — every position, every committee analysis, every vote — loaded, indexed, and queryable from day one.

Pre-2019? Not in RTG yet — but it's on the roadmap. Backfilling California's earlier sessions is on our list, and every RTG customer can see the roadmap from inside the product. If pre-2019 history is critical to your work today, mention it on the kickoff call — customer demand is what moves priorities.

Strongly recommended. The 14-day trial overlaps with your existing contract on purpose. Most teams bringing data run parallel for the full 14 days, then cancel their old tool once they're confident RTG carries the daily workflow.

The entire trial period is the parallel-run window by design — we don't ask you to commit until day 14, and even then “continue monthly” is an honest option.

It's real. We've seen it. The most common pattern: one or two on the team push the switch, others are skeptical until they see Day 3 of the migration. The training session covers exactly the differences from their current daily workflow — not generic feature demos.

For teams of 5+, we offer a second training session at the two-week mark to address the specific friction points the team has actually hit in practice, rather than theoretical ones.

There isn't one. No credit card to start, the full product unlocked for 14 days, cancel anytime, and RTG is built to be left — every exportable field comes with you if you go.

RTG is road-tested. Not a demo, not a pre-release, not a preview of something still being built: three-plus years of live California sessions, on real deadlines, in the hands of teams doing the actual work. It's built by engineers from Cirkadia, a studio that has shipped production software for 30 years. Every headline capability on this site is in production, not in development, and where something of ours is still being built we say so and put it on the roadmap where you can watch it move. We would rather be judged on what runs today than on what's promised for next year.

What we trade on: shipping speed, modern UX, and a feature set built directly from Capitol client conversations — months of development, not years. The same lean team you'd talk to about a bug today is the team that shipped the feature you used yesterday.

The first 14 days, however you start.