Roy, built for your industry — or just for you.
The self-serve plans speak mail, calendar, chat, calls and the tools most people share. If your day runs on software Roy doesn't speak yet — an industry system, or one only your company has — this is the plan. Every person still runs Roy on their own machine; nothing about that changes.
An industry with its own software.
Roy adapted to the systems your industry already runs on — practice, case, property or dealer management, an EHR, an ERP — plus the workflows, retention rules and approval tiers that industry expects.
- Read from the system of record — the patient, matter, unit or deal, alongside mail and calendar.
- Industry workflows — intake, scheduling, follow-up, renewal — as Roy routines with the right gates.
- Retention and audit the way your regulator expects, on top of Roy's own log.
- Rolled out to a team with the same rules per person and an optional shared view for a lead.
Good fit when: several people in one industry, one or two dominant systems, workflows that repeat.
A new industry, or company-specific software.
Integrations and workflows built for your own systems — internal tools, proprietary databases, bespoke approval chains — with Roy's specialists configured to your roles.
- Integrations written for you — your APIs, your databases, your file shares, read-safe and write-gated like everything else.
- Your approval chain — who can approve what, in which order, with which limits.
- Specialists for your roles — the research, product and sales pods reshaped around how your company actually works.
- A named engineer through discovery, build and the first month live.
Good fit when: the software is yours, the workflow is unusual, or nobody has built an agent for your line of work yet.
Local-first, gated, audited — for every person on the team.
Enterprise doesn't move Roy into a cloud. Each person runs it on their own machine with their own keys; the custom integrations run there too. What we add is the connection to your systems, the rules your organization needs, and the people to set it up.
- Everything in Personal + WorkTwo mailboxes, one queue, both lives kept apart — for each person.
- An organization, with members and rolesOwners, admins and members; invites by code; each person's Roy is their own — admins never read a member's mail.
- A playbook per roleWhat Roy may do for whom: reads are on, everything outward is a grant the role holds or doesn't.
- Finance roles and org approvalsRequester, approver, finance owner, viewer. A company's payment and invoice drafts reach the people who can act on them — on their own phone — with two signatures above the threshold.
- Support access you grantTime-boxed, logged, revocable. Export or delete the organization's data from Settings.
- Onboarding, priority support, volume pricingPer seat; the number depends on how much we build.
How it goes
- You tell us about your setupThe form below — five minutes. A person reads it.
- A conversationWhich systems, which workflows, how many people, what has to stay where.
- A written scope and a priceSemi-custom is usually weeks; fully custom depends on the systems.
- Build, pilot with a few people, roll outThe same gates from day one; nothing goes live unreviewed.
Five questions. A person replies.
No sales sequence, no calendar link. Say what you run and what you'd want Roy to handle; we'll write back from a real address.