Vulcan's Deployments page names statewide deployments in Louisiana (20 departments and offices) and Arkansas (16), plus 14 more agencies, from the North Carolina General Assembly to Mississippi's Division of Medicaid and Oklahoma DEQ. It says nothing about what any of them did. The 48 agency and workflow pages, the government page and the commercial page show no customer names, metrics or case studies either, so a licensing board reading the licensing page never learns that a commerce department already uses Justinian. The only outcome on the site is Trajan's TREO.Texas.gov launch (50 agencies, 1,427 workflows). Its closest service-delivery rival, Polimorphic, leads with named case studies and numbers.
First action
Email the five most engaged agency contacts this week, asking for one number and permission to publish.
How to measure it
Briefing requests from /gov pages
- Now
- –
- Target
- +30%
- By
- 90 days
Steps
Pick five
One named customer per agency type, matched to a /gov/for page.
Co-Founder & CEO 1 day
Ask permission
Approval for name, logo, quote and one number; anonymised fallback.
Deployed Agent Orchestrator 2 weeks
Pull the numbers
Usage, rules reviewed, hours or turnaround from each deployment.
Deployed Agent Orchestrator 3 days
Write the stories
Problem, workflow, number, quote; 300 words each.
Co-Founder & CEO 1 week
Publish and link
/deployments pages linked from /gov/for, /gov workflow and briefing pages.
Agent Orchestrator 2 days
Add numbers to logos
One result under each homepage logo.
Agent Orchestrator 1 day
Arm the SDR
Use each story in outreach to similar agencies.
SDR / BDR ongoing
Measure
Briefing requests by landing page, before and after.
Co-Founder & CEO monthly
Why it works
Write a short deployment story for five named customers, one per agency type: a legislature, an environmental agency, a health or Medicaid agency, a commerce or licensing department and a governor's office. Each story covers the problem, the workflow used, one number (rules inventoried, hours saved, turnaround, questions answered) and a quote if the agency approves. Publish each at /deployments/<agency>. Link it from the matching /gov/for page and from one or two /gov workflow pages (the environment page shows the environmental agency's story, the licensing page shows the commerce story) and from the briefing pages. Put one number under each logo on the homepage strip. Where an agency cannot approve a named quote, publish it as "a state environmental agency" with the agency's consent. Expand from five stories to every deployment over the quarter.
Public-sector buyers ask first who like them already uses a product. A matching peer story on the page they landed on answers that before the briefing, makes the "Request Briefing" click feel safe, and gives the new SDR a reason to call similar agencies.
Ready to use
CopyDeployment story template
Agency type: [legislature / environment / health / commerce / governor] The problem: [one sentence in the agency's words] What they use: [Justinian workflow or Trajan] One number: [rules inventoried / hours saved / turnaround / questions answered] Quote: [approved, with title] Links from: /gov/for/<type>, /gov/<workflow>, /government/briefing/<audience> CTA: Request a briefing like this one
Risks and how to handle them
Agencies need communications office approval
Start with anonymised stories and ask for the named version later.
Early numbers are small
Use scope (departments, workflows, rules covered) until outcomes mature.
Evidence
- Your websiteDeployments page: statewide deployments in Louisiana ("20 departments and offices") and Arkansas (16 departments and offices), plus 14 named state agencies and offices, including the North Carolina General Assembly, Utah Department of Commerce, Oklahoma DEQ, Mississippi Division of Medicaid, the Georgia and West Virginia governors' offices, Virginia's Office of Regulatory Management and Idaho's Legislative Services Office. No description, quote, result or case study for any of them.Source
- Your websiteAgency and workflow pages (48 under /gov): the red tape page ("Count the restrictions. Then remove the dead ones.", for "Regulatory efficiency offices, executive teams running a reduction mandate, and rule review staff") and the licensing boards page have example queries and a product film but no named customers, metrics or case studies; neither mentions Virginia or Texas.Source
- Your websiteTrajan page: "All government services, one AI concierge." The proof is the Texas launch of TREO.Texas.gov, "The nation's first government AI concierge for citizens", a free public service covering 50 agencies and 1,427 workflows; CTA "Book a Trajan briefing".Source
- Your websiteGovernment page: "AI agents purpose built for government"; "32 kinds of work · 16 kinds of agency"; a "13states" figure in the header with no explanation; no case studies, customer names, testimonials or outcome metrics; no contract vehicles or pricing; primary CTA "Request Briefing".Source
- Competitor researchPolimorphic's homepage ("Better Service, From Front Door to Back Office"): AI voice, chat, workflows and CRM for local and state government, with dozens of government logos, named case studies with numbers (Suisun City about 40 staff hours reclaimed a month; Littleton, CO calls cut by 50%), named testimonials and a downloadable ROI guide.Source