ProgrammableMarketing/vulcan.ai (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 7
  • This quarter · 11
  • Big bets · 3
  • Wildcards · 1
Generated Nov 9, 2026 1 view
  1. Programmable
  2. Playbooks
  3. Vulcan Technologies
Vulcan Technologies logo

growth playbook · Nov 9, 2026

vulcan.ai (opens in a new tab)

Vulcan Technologies growth playbook

Diagnosis

Vulcan has more traction than its website admits. Its Deployments page names statewide deployments in Louisiana (20 departments) and Arkansas (16), plus 14 more agencies, and TREO.Texas.gov is a live public product. The release notes show weekly shipping. Yet none of the 48 agency and workflow pages, the government page or the commercial page shows a single customer result.

The RSS feed stopped in July. The benchmark win over Lexis and Westlaw has no published method. Buyers are pushed to a briefing with no proof, no buying route and no price. The hiring is small and pointed: an SDR/BDR, a Deployed Agent Orchestrator who travels weekly, and an Agent Orchestrator. That means outbound and on-site deployment are the growth engine.

This playbook first puts the existing deployments, press and security status where buyers read them. It then gives the new SDR triggers from Justinian's own monitoring, turns pilots into expansions and case studies, and opens the commercial market with a public sample and, later, a priced starter plan.

Growth Score

7/10

Biggest Opportunity

Turn 50 named government deployments and the Texas launch into visible, peer-to-peer proof, then expand statewide from the governors' offices already on board.

Biggest Risk

Government cycles are long and depend on a few champions, and better-proven rivals (Polimorphic for service delivery, Quorum for policy teams, Lexis and Westlaw for legal research) win the evaluations while Vulcan's results stay invisible.

01

Start here

The three moves to make first. Each one is written up in full below.

  1. 1

    Turn the 50 named deployments into proof on the pages buyers read: one outcome story per agency type, linked from the matching agency page

    Email the five most engaged agency contacts this week, asking for one number and permission to publish.

    High impact First result in 1 month
  2. 2

    Put the press on the pages it proves: link the Texas launch and the coverage from the permitting, licensing and red-tape pages

    Add the StateScoop Texas summary to the permitting and licensing pages.

    Medium impact First result in 1 month
  3. 3

    Fix the RSS feed and add a release-notes hub: four releases since July never reached subscribers

    Add the four missing releases to rss.xml.

    Medium impact First result in 2 weeks

02

Your idea portfolio

22 ideas, grouped by when to run them. Open any idea for how to run it: the steps, who to approach, copy you can use, and how to measure it.

  • 7 ideas are marked Unexpected: plays you are unlikely to have tried.

Every idea placed by the effort it takes against the impact it could have. Quick wins sit top left; select a number to open that idea. The filters below narrow the list by status, timing, category and what Programmable can build.

Effort vs impactEach number is an idea. Select one to open it.
Impact →
Quick wins · 1Big bets · 10Fill-ins · 6Reconsider · 5
Effort →

Showing 22 of 22 ideas

This week 7

Quick wins with a clear first action.

  • 01

    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.

    High impactMedium effort First result in 1 month Co Founder & CEO

    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

    1. 1

      Pick five

      One named customer per agency type, matched to a /gov/for page.

      Co-Founder & CEO 1 day

    2. 2

      Ask permission

      Approval for name, logo, quote and one number; anonymised fallback.

      Deployed Agent Orchestrator 2 weeks

    3. 3

      Pull the numbers

      Usage, rules reviewed, hours or turnaround from each deployment.

      Deployed Agent Orchestrator 3 days

    4. 4

      Write the stories

      Problem, workflow, number, quote; 300 words each.

      Co-Founder & CEO 1 week

    5. 5

      Publish and link

      /deployments pages linked from /gov/for, /gov workflow and briefing pages.

      Agent Orchestrator 2 days

    6. 6

      Add numbers to logos

      One result under each homepage logo.

      Agent Orchestrator 1 day

    7. 7

      Arm the SDR

      Use each story in outreach to similar agencies.

      SDR / BDR ongoing

    8. 8

      Measure

      Briefing requests by landing page, before and after.

      Co-Founder & CEO monthly

    First result
    1 month
    Cost
    Staff time; agency communications approvals
    Owner
    Co Founder & CEO

    Smallest test

    Publish the TREO.Texas.gov launch as a full case study and link it from the permitting and licensing pages this week.

    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
  • 02

    Vulcan has real third-party coverage: StateScoop on the Texas partnership (May 2026), Fortune (September 2025), the $10.9M seed (AP, Axios Pro, Law360), and Route Fifty's account of Virginia's 2025 executive order requiring agentic AI in regulatory review. All of it sits on one page of headlines and dates. The red tape page, written for "Regulatory efficiency offices", mentions neither Virginia nor Texas.

    Medium impactLow effort First result in 1 month Marketing lead

    First action

    Add the StateScoop Texas summary to the permitting and licensing pages.

    How to measure it

    Briefing rate on press-linked pages

    Now
    –
    Target
    +15%
    By
    60 days

    Steps

    1. 1

      Summarise

      Two lines per article, with the outlet and date.

      Marketing lead 1 day

    2. 2

      Map to pages

      Each article to the workflow and agency pages it supports.

      Marketing lead 2 hours

    3. 3

      Add the blocks

      "As covered in" snippets on mapped pages.

      Agent Orchestrator 1 day

    4. 4

      Upgrade /resources

      Summaries and links to product pages.

      Agent Orchestrator 1 day

    5. 5

      Homepage bar

      Outlet logos with links.

      Agent Orchestrator 2 hours

    6. 6

      Measure

      Briefing rate on changed pages.

      Marketing lead monthly

    First result
    1 month
    Cost
    $0
    Owner
    Marketing lead

    Smallest test

    Add one press snippet to the red tape page today.

    Why it works

    Write a two-line summary of each article and place it where it proves something. The Texas partnership goes on the Trajan, permitting, licensing and constituent-services pages. The regulatory review coverage goes on the red tape, rulemaking and governor pages. The seed round goes on the commercial and startups pages. Add a small "As covered in" bar to the homepage and briefing pages. Upgrade /resources from headlines to summaries with the related product page linked.

    Independent coverage is trusted more than vendor copy, and placing it on the page a buyer is reading lifts conversion more than a separate press page that few visit.

    Risks and how to handle them

    • Older coverage describes earlier positioning

      Quote only what still holds, and date every snippet.

    Evidence

    • Your websiteMedia Coverage page: StateScoop, May 15, 2026, "Vulcan partners with Texas, delivering AI to help public navigate regulations, permits, and licenses"; Fortune, September 16, 2025; a $10.9M seed round announced October 9, 2025 (General Catalyst, AP, Axios Pro, Law360, Austin Business Journal). The page lists headlines and dates only.Source
    • Press coverageRoute Fifty (August 22, 2025): Virginia's governor signed a July 2025 executive order saying the commonwealth "must use" agentic AI to streamline its regulations; Vulcan built a central database of Virginia's regulations, statutes and case law whose agents flag discrepancies, such as a fine enforced above the statutory amount under a repealed rule; Vulcan was incorporated in April 2025 and won the contract in May.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
  • 03

    Justinian ships fast: 24 release-note pages, the newest 3.1.0 on November 6 with Mail, GIS and CAD built in. But the RSS feed's newest item is 2.2.1 from July 30, so 2.4.0, 2.5.0, 3.0.0 and 3.1.0 never reached anyone following the feed. Each release note links only back to the press page, and there is no release-notes index. The footer links one release at a time.

    Medium impactLow effort First result in 2 weeks Agent Orchestrator

    First action

    Add the four missing releases to rss.xml.

    How to measure it

    Accounts trying a new feature within 30 days

    Now
    –
    Target
    40%
    By
    90 days

    Steps

    1. 1

      Fix the feed

      Generate rss.xml from the release pages.

      Agent Orchestrator 1 day

    2. 2

      Build the index

      /justinian/releases with dates and summaries.

      Agent Orchestrator 1 day

    3. 3

      Link it

      Footer, product page and each release note.

      Agent Orchestrator 2 hours

    4. 4

      Tidy old slugs

      Redirect or label the older version series.

      Agent Orchestrator 2 hours

    5. 5

      Monthly email

      To agency admins and champions, with one workflow to try.

      Deployed Agent Orchestrator monthly

    6. 6

      Track adoption

      Use of new features by account.

      Co-Founder & CTO monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Agent Orchestrator

    Smallest test

    Fix the feed today and send one 3.1.0 email to champions.

    Why it works

    Regenerate the feed from the same source as the release pages so every release publishes automatically. Add /justinian/releases, a dated index with a one-line summary per release and filters by area (corpus, agents, security, apps). Link it from the footer and the product page. Send a monthly "What's new in Justinian" email to admins and champions at deployed agencies, with one workflow to try. Tidy the older version slugs so the series reads in order.

    Weekly shipping is proof of momentum for buyers and a reason for existing users to try new features. Agency champions who see new capabilities expand use, and evaluators see a living product.

    Risks and how to handle them

    • Too many emails for busy staff

      Monthly digest only, one action per email.

    Evidence

    • Your websiteRelease notes: 24 Justinian update pages in the sitemap, the newest 3.1.0 (November 6, 2026); a release note links only back to /resources and there is no release-notes index. The RSS feed's newest item is 2.2.1 (July 30, 2026); 2.4.0, 2.5.0, 3.0.0 and 3.1.0 are not in it.Source
    • Your websiteJustinian 3.1.0 (November 2026): Mail (connects Gmail or Outlook, drafts replies, and each send needs an approval card; users can also forward or CC threads to a Justinian address), GIS (shapefiles, geodatabases, KML; spatial questions such as which parcels fall in a flood zone) and a browser CAD editor for DXF and DWG files.Source
    • App StoreJustinian iOS app (Vulcan Technologies, Inc.): 5.0 from 6 ratings; free, but usable only by organizations with an active Vulcan agreement, with access provisioned by the organization's administrator; version 2.6.5 updated November 2026.Source
  • 05

    The security page describes TX-RAMP carefully as "Aligned to Texas state agency security requirements". The commercial page lists TX-RAMP next to SOC 2 and ISO 27001, which reads like a certification, and the state briefing page offers a "TX-RAMP / FedRAMP posture" discussion. Security reviewers compare wording line by line, and a mismatch can slow a review. Separately, the SOC 2 report, ISO certificate and FedRAMP package are all "by request" with no single form.

    Medium impactLow effort First result in 1 month Security and compliance lead

    First action

    Change the TX-RAMP line on the commercial page to match the security page.

    How to measure it

    Security review cycle time

    Now
    –
    Target
    -20%
    By
    2 quarters

    Steps

    1. 1

      Audit wording

      Every page that mentions FedRAMP, SOC 2, ISO or TX-RAMP.

      Security and compliance lead 1 day

    2. 2

      Fix copy

      One sentence per status, reused everywhere.

      Agent Orchestrator 1 day

    3. 3

      Status table

      On /security, with dates.

      Security and compliance lead 1 day

    4. 4

      Request form

      Routed to the security lead and SDR.

      Agent Orchestrator 1 day

    5. 5

      Standard packet

      NDA, reports and FAQ ready to send.

      Security and compliance lead 1 week

    6. 6

      Track

      Requests and days to approval by deal.

      SDR / BDR monthly

    First result
    1 month
    Cost
    $0
    Owner
    Security and compliance lead

    Smallest test

    Fix the commercial page wording today.

    Why it works

    Use one wording for each item across the site. Add a status table to /security: FedRAMP Ready (Marketplace listing, pursuing full authorization), SOC 2 (report on request), ISO 27001 (certificate on request), TX-RAMP (the exact current status), penetration test summary, and the architecture review. Add one request form (agency, role, documents needed, procurement timeline) that routes to the SDR and the security lead and sends a standard NDA where needed.

    Security review is the longest step in a government AI deal. Precise, consistent status earns reviewers' trust, and a single form turns document requests into tracked pipeline.

    Risks and how to handle them

    • Status changes as audits progress

      Date the table and update it at each milestone.

    Evidence

    • Your websiteSecurity page: "Vulcan is FedRAMP® Ready", listed on the FedRAMP Marketplace "as we pursue full authorization"; SOC 2 report and ISO 27001 certificate available by request; TX-RAMP described as "Aligned to Texas state agency security requirements for public-sector deployments". The commercial page lists SOC 2, ISO 27001, TX-RAMP and private deployment side by side, and the state agencies briefing page offers a "TX-RAMP / FedRAMP posture" discussion.Source
    • Your websiteState agencies briefing page: "Your statutes, your regulations, and the federal authority they implement — one corpus."; the agenda covers a live walkthrough on the agency's own rules, a monitoring demo, a comparison with other states, and deployment, security posture and pilot scoping; the form asks for focus areas (Justinian or Trajan); no customer proof.Source
  • 06

    The homepage headline and the description search results show are the same mission line: "VULCAN strengthens America's social contract by safely shepherding frontier AI to government." It does not say what Vulcan does (legal and regulatory research, red tape reduction, permitting, a citizen concierge). The government page shows a "13states" figure with no label, while the Deployments page names agencies in about a dozen states, including two statewide deployments.

    Medium impactLow effort First result in 3 weeks Marketing lead

    First action

    Rewrite the homepage meta description.

    How to measure it

    Search click-through

    Now
    –
    Target
    +15%
    By
    60 days

    Steps

    1. 1

      List queries

      Top queries from Search Console.

      Marketing lead 2 hours

    2. 2

      Rewrite homepage

      Description and subhead.

      Marketing lead 2 hours

    3. 3

      Label the number

      "Deployed in 13 states", linked to Deployments.

      Agent Orchestrator 1 hour

    4. 4

      Rewrite sections

      Government and commercial descriptions.

      Marketing lead 2 hours

    5. 5

      Check previews

      Link previews in email and social.

      Agent Orchestrator 1 hour

    6. 6

      Measure

      Click-through by page.

      Marketing lead monthly

    First result
    3 weeks
    Cost
    $0
    Owner
    Marketing lead

    Smallest test

    Change the homepage description today.

    Why it works

    Keep the mission as the headline if wanted, but rewrite the meta description and add a plain subhead: what Justinian and Trajan do, for whom, and one proof point (statewide in Louisiana and Arkansas, FedRAMP Ready). Label the 13-state figure ("Deployed in 13 states") and link it to the Deployments page. Do the same for the government and commercial descriptions, and test the change in Search Console.

    Buyers search for the job ("AI for regulatory review", "permitting AI for state agencies"), and a description that matches the query lifts click-through. A labelled number is proof; an unlabelled one is noise.

    Risks and how to handle them

    • Losing the mission voice

      Keep the mission headline; change only the description and subhead.

    Evidence

    • Your websiteHomepage: headline "VULCAN strengthens America's social contract by safely shepherding frontier AI to government.", which is also the description search results show; two products, JUSTINIAN ("an AI agent for government knowledge workers") and TRAJAN ("a public-facing AI concierge built to modernize government service delivery"); a "Deployed in government" strip of 15 agency logos; "FedRAMP Ready in AWS GovCloud (US)"; no statistics, testimonials or case studies.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
    • 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
  • 07

    The homepage is fast: real visitors pass Core Web Vitals and mobile scores 96. But Google's audit flags two accessibility problems: low colour contrast and no main landmark for screen readers. Trajan is a public-facing concierge hosted on government websites for every citizen, and agencies ask vendors how public-facing tools serve people with disabilities. Vulcan's site has no accessibility page to point to.

    Medium impactLow effort First result in 2 weeks Agent Orchestrator

    First action

    Fix the contrast colours and add the main landmark.

    How to measure it

    Lighthouse accessibility score

    Now
    –
    Target
    100
    By
    30 days

    Steps

    1. 1

      Fix the template

      Contrast and main landmark.

      Agent Orchestrator 1 day

    2. 2

      Compress images

      Homepage images (514 KB).

      Agent Orchestrator 2 hours

    3. 3

      Test Trajan

      Screen reader and keyboard only.

      Agent Orchestrator 2 days

    4. 4

      Fix findings

      Citizen chat and smart forms.

      Co-Founder & CTO 1 week

    5. 5

      Publish statement

      Target, method, gaps, contact.

      Security and compliance lead 1 day

    6. 6

      Add to packet

      Conformance report in the security request packet.

      Security and compliance lead 1 day

    First result
    2 weeks
    Cost
    Staff time; optional external audit
    Owner
    Agent Orchestrator

    Smallest test

    Fix the homepage contrast and rerun PageSpeed.

    Why it works

    Fix the contrast and add a main landmark across the site template. Then test Trajan's citizen interface with a screen reader and keyboard only, and publish an accessibility statement covering conformance target, testing method, known gaps and a contact. Add an accessibility conformance report for Trajan to the security request packet. While in the template, compress the homepage images (514 KB of savings).

    For a vendor whose product faces the public, accessibility is part of the buying checklist. Answering it up front removes a late-stage blocker and shows care.

    Risks and how to handle them

    • Testing finds bigger issues in Trajan

      Publish known gaps with fix dates; that is better than silence.

    Evidence

    • PageSpeedGoogle PageSpeed (November 9, 2026): mobile performance 96, desktop 100; real visitors pass Core Web Vitals (field LCP 1.27 s, CLS 0); the homepage downloads 4.3 MB with 514 KB of image savings available; accessibility 93, with two issues: "Background and foreground colors do not have a sufficient contrast ratio" and "Document does not have a main landmark".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
  • 15

    The corpus page invites visitors to request missing sources. Someone asking for a specific state's environmental dataset or a city's code has just told Vulcan their exact job and need. A new SDR is joining, and today these requests most likely go to a data backlog rather than to sales.

    Medium impactLow effort First result in 2 weeks SDR / BDR

    First action

    Export the last 90 days of data requests and reply to the open ones.

    How to measure it

    Data-request-to-briefing rate

    Now
    –
    Target
    20%
    By
    60 days

    Steps

    1. 1

      Export requests

      Last 90 days.

      SDR / BDR 1 hour

    2. 2

      Route new ones

      To the SDR and data team.

      Agent Orchestrator 2 hours

    3. 3

      Add fields

      Organisation and role, optional.

      Agent Orchestrator 1 hour

    4. 4

      Reply template

      Closest source, ETA, briefing offer.

      SDR / BDR 2 hours

    5. 5

      Notify on ship

      Personal email when the source lands.

      SDR / BDR ongoing

    6. 6

      Track

      Requests, replies and briefings.

      SDR / BDR monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    SDR / BDR

    Smallest test

    Reply personally to this week's requests.

    Why it works

    Route each data request to the SDR as well as the data team, with the requester's organisation and the source asked for. Reply within a day with what Vulcan already has that is closest, an estimated date for the new source, and an offer of a short briefing on that topic. When the source ships, email the requester personally. Add an optional "organisation and role" field to the request form.

    A visitor who asks for data has stated intent and a use case. A fast, specific reply converts far better than a generic demo request, and shipping their source creates goodwill.

    Risks and how to handle them

    • Requests from researchers with no budget

      Reply to all, but prioritise organisation domains.

    Evidence

    • Your websiteCorpus page: "157,000,000,000 records. One corpus."; 141 source families in 15 categories and 51 jurisdictions; each source has its own page, but only some entries give record counts and only some show a date range; a "Missing something? Tell us what to add" link to a data request form.Source
    • HiringCareers page (checked November 9, 2026): four open roles, all in Austin, TX: Agent Orchestrator (Engineering), Deployed Agent Orchestrator (Engineering / GTM, weekly travel), SDR / BDR (GTM) and Executive Assistant (Operations); titles only, no role descriptions; the page says "Build the infrastructure for AGI-era government and law."Source

This quarter 11

The core plays for the next three months.

  • 04

    The 2.1.9 release note says Vulcan benchmarked 50-state surveys against Lexis, Westlaw and four general-purpose AI assistants, and that "Justinian won on both speed and accuracy". No method, test set or numbers are published. The buyers who most need convincing (law firms, in-house counsel and agency general counsel) are trained to distrust claims they cannot check. Quorum, by contrast, publishes hours-saved figures and review ratings.

    High impactMedium effort First result in 2 months Co Founder & CTO

    First action

    Write up the method used for 2.1.9 and see what can be published as-is.

    How to measure it

    Commercial briefing requests

    Now
    –
    Target
    +25%
    By
    2 quarters

    Steps

    1. 1

      Document the method

      Questions, answer key, scoring and timing.

      Co-Founder & CTO 1 week

    2. 2

      Attorney review

      Outside attorneys check the answer key.

      Co-Founder & CEO 2 weeks

    3. 3

      Rerun

      Current versions of every tool, on the same day.

      Agent Orchestrator 1 week

    4. 4

      Legal review

      Comparative claims and trademarks.

      Co-Founder & CEO 1 week

    5. 5

      Publish

      Results, method and question set.

      Agent Orchestrator 2 days

    6. 6

      Pitch

      Legal-tech press and bar publications.

      Marketing lead 2 weeks

    7. 7

      Repeat

      Twice a year.

      Co-Founder & CTO 6 months

    First result
    2 months
    Cost
    Attorney review fees plus staff time
    Owner
    Co Founder & CTO

    Smallest test

    Publish the question set and Justinian's own scores first.

    Why it works

    Publish a benchmark page: 25-50 real 50-state questions across topics, how the answer key was built and checked by licensed attorneys, scoring for accuracy, citation validity and time, and the results by tool. Release the question set so others can rerun it. Repeat the benchmark twice a year and after big releases. Use the page in commercial briefings, on the law-firm and in-house pages, and as a pitch to legal press.

    A reproducible benchmark turns a claim into evidence. It is linkable, it gets cited in legal-tech coverage, and it gives sales a neutral document to send to sceptical reviewers.

    Risks and how to handle them

    • Results narrow on rerun

      Publish anyway with honest margins; precision builds more trust than a sweep.

    • Competitor objections

      Open method and question set; invite reruns.

    Evidence

    • Your websiteJustinian 2.1.9 release note (July 2026): "We benchmarked 50-state surveys against Lexis, Westlaw" and four general-purpose AI assistants; "Justinian won on both speed and accuracy." No method, test set or numbers are published.Source
    • Your websiteCommercial page: "For teams that have to get it right."; six paths (law firms, regulatory and compliance, policy, trade associations, in-house counsel, startups); "157,000,000,000 records across 141 source families"; no pricing, trial or self-serve sign-up, and no logos or testimonials; every path, including startups, ends in "Book a briefing".Source
    • Competitor researchQuorum's homepage: "AI For Your Government Affairs Team"; "Trusted by 2,000+ Policy Teams Nationwide"; a G2 rating of 4.3 from 180 reviews; claims of 10+ hours saved per customer per week; named AI agents for bill tracking and meeting prep.Source
  • 08

    Every government and commercial page ends in "Request Briefing", and the state briefing agenda already includes "pilot scoping". Nowhere does the site say how an agency actually buys: no contract vehicles, no pilot shape, no price range, no timeline. A program manager who likes the demo still has to convince procurement, with nothing to forward.

    High impactMedium effort First result in 1 quarter Co Founder & CEO

    First action

    Write down the last three deals' path from briefing to signature.

    How to measure it

    Briefing-to-pilot rate

    Now
    –
    Target
    +20%
    By
    2 quarters

    Steps

    1. 1

      Map past deals

      Steps, documents and timing for recent wins.

      Co-Founder & CEO 2 days

    2. 2

      Define the pilot

      Standard length, scope and success measures.

      Deployed Agent Orchestrator 3 days

    3. 3

      List routes

      Purchasing routes Vulcan can use today.

      Co-Founder & CEO 2 days

    4. 4

      Write the page

      Plus a one-page procurement summary and draft scope of work.

      Marketing lead 1 week

    5. 5

      Link it

      From every briefing page and the government page.

      Agent Orchestrator 1 day

    6. 6

      Use in follow-up

      Sent after every briefing.

      SDR / BDR ongoing

    7. 7

      Measure

      Days and conversion from briefing to pilot.

      Co-Founder & CEO monthly

    First result
    1 quarter
    Cost
    Staff time
    Owner
    Co Founder & CEO

    Smallest test

    Send a one-page buying guide after the next five briefings.

    Why it works

    Publish /government/how-to-buy. It explains the standard pilot (length, scope, success measures, what the agency provides) and the typical path from briefing to pilot to statewide agreement. It lists the purchasing routes Vulcan can use today and links the security status table. Add a downloadable one-page summary for procurement officers and a draft scope of work they can adapt. Offer a price range or the pilot price if the founders are comfortable; if not, state what drives price (users, agencies, deployment type).

    Government buyers stall on process, not interest. Giving the champion a forwardable buying path shortens the cycle and screens out tyre-kickers before the briefing.

    Risks and how to handle them

    • Publishing price limits negotiation

      Publish the pilot price and the price drivers, not enterprise rates.

    Builds on

    Evidence

    • 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
    • Your websiteState agencies briefing page: "Your statutes, your regulations, and the federal authority they implement — one corpus."; the agenda covers a live walkthrough on the agency's own rules, a monitoring demo, a comparison with other states, and deployment, security posture and pilot scoping; the form asks for focus areas (Justinian or Trajan); no customer proof.Source
    • Your websiteSecurity page: "Vulcan is FedRAMP® Ready", listed on the FedRAMP Marketplace "as we pursue full authorization"; SOC 2 report and ISO 27001 certificate available by request; TX-RAMP described as "Aligned to Texas state agency security requirements for public-sector deployments". The commercial page lists SOC 2, ISO 27001, TX-RAMP and private deployment side by side, and the state agencies briefing page offers a "TX-RAMP / FedRAMP posture" discussion.Source
  • 09

    Vulcan is hiring its first SDR/BDR. Its own product already "keeps watch" on statutes, regulations and federal actions across 50 states. Virginia's executive order requiring agentic AI in regulatory review shows what a buying trigger looks like, and the red tape page is written for exactly those offices. A cold list of agencies wastes a new SDR; a list of agencies that just got a reduction mandate, a new permitting law or a sunset review does not.

    High impactMedium effort First result in 1 month SDR / BDR

    First action

    Write the monitor query for red-tape and permitting-reform actions in the last 90 days.

    How to measure it

    Trigger-sourced briefings

    Now
    –
    Target
    8 a month
    By
    90 days

    Steps

    1. 1

      Define triggers

      Mandates, new offices, reform laws, sunset reviews.

      Co-Founder & CEO 1 day

    2. 2

      Build the monitor

      Weekly Justinian job with source text.

      Agent Orchestrator 1 week

    3. 3

      Find the office

      Responsible agency and role for each trigger.

      SDR / BDR weekly

    4. 4

      Draft the analysis

      Two paragraphs on that state's rules.

      SDR / BDR weekly

    5. 5

      Reach out

      Trigger, analysis, briefing offer.

      SDR / BDR weekly

    6. 6

      Hand off

      Booked briefings to the founders.

      SDR / BDR ongoing

    7. 7

      Learn

      Conversion by trigger type.

      Co-Founder & CEO monthly

    First result
    1 month
    Cost
    SDR time; existing product
    Owner
    SDR / BDR

    Smallest test

    Run the monitor once and send ten trigger emails.

    Why it works

    Set up a standing Justinian monitor for buying signals: executive orders or bills creating red-tape reduction targets, new regulatory-efficiency offices, permitting reform laws, licensing overhauls and legislative sunset reviews. Each week it produces a short list with the triggering text and the responsible office. The SDR opens with the trigger and a two-paragraph Justinian analysis of that state's rules (for example, how many provisions lack live authority), and offers a briefing. Track which triggers convert.

    Outreach tied to a mandate the buyer just received is timely and relevant. Showing the product's own analysis in the first email is a demo before the demo.

    Risks and how to handle them

    • Analysis errors in cold outreach

      Founder review of every analysis for the first month.

    Evidence

    • HiringCareers page (checked November 9, 2026): four open roles, all in Austin, TX: Agent Orchestrator (Engineering), Deployed Agent Orchestrator (Engineering / GTM, weekly travel), SDR / BDR (GTM) and Executive Assistant (Operations); titles only, no role descriptions; the page says "Build the infrastructure for AGI-era government and law."Source
    • Your websiteJustinian page: "1 agent becomes 50" (50-state research that cites every statute to its source and keeps watch on changes), permitting, Vulcan Office, and app building inside the agency boundary; available on the web, macOS and Windows apps, Slack, Teams and email; a "Request Briefing" form; no pricing and no customer proof.Source
    • Press coverageRoute Fifty (August 22, 2025): Virginia's governor signed a July 2025 executive order saying the commonwealth "must use" agentic AI to streamline its regulations; Vulcan built a central database of Virginia's regulations, statutes and case law whose agents flag discrepancies, such as a fine enforced above the statutory amount under a repealed rule; Vulcan was incorporated in April 2025 and won the contract in May.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
  • 10

    Two states run Vulcan statewide: 20 departments and offices in Louisiana, 16 in Arkansas, each starting from the governor's office. The Deployments page also lists the Georgia and West Virginia governors' offices as single-office customers. These have the same executive sponsor that made the statewide deals work, but have not yet expanded.

    High impactMedium effort First result in 1 quarter Co Founder & CEO

    First action

    Interview the Louisiana and Arkansas sponsors about what made statewide work.

    How to measure it

    Single-office states moved to multi-department

    Now
    –
    Target
    2
    By
    2 quarters

    Steps

    1. 1

      Document the model

      Sponsor, sequence, security, outcomes.

      Co-Founder & CEO 1 week

    2. 2

      Pick departments

      Best-fit departments for each single-office state.

      Deployed Agent Orchestrator 1 week

    3. 3

      Build proposals

      90-day rollout and statewide price.

      Co-Founder & CEO 2 weeks

    4. 4

      Line up peers

      Reference calls from statewide customers.

      Co-Founder & CEO 2 weeks

    5. 5

      Present

      At each account's next review.

      Co-Founder & CEO 1 month

    6. 6

      Roll out

      On-site onboarding department by department.

      Deployed Agent Orchestrator 1 quarter

    First result
    1 quarter
    Cost
    Travel and staff time
    Owner
    Co Founder & CEO

    Smallest test

    Pitch one additional department in one single-office state.

    Why it works

    Write down the statewide playbook from Louisiana and Arkansas: who sponsored it, which departments came first, how security was approved once for all, and what the governor's office got (a cross-agency rule inventory, a red-tape dashboard). Turn it into a short proposal for each single-office customer: the departments most likely to benefit, a 90-day rollout plan and a statewide price. Present it at each account's next review, with an introduction to a peer in Louisiana or Arkansas where they agree.

    Expansion inside a state with an existing sponsor and approved security is far faster than a new state, and a peer reference from another governor's office carries real weight.

    Risks and how to handle them

    • Budget cycles delay expansion

      Start with departments that can buy under existing authority, and plan for the next budget.

    Builds on

    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 websiteHomepage: headline "VULCAN strengthens America's social contract by safely shepherding frontier AI to government.", which is also the description search results show; two products, JUSTINIAN ("an AI agent for government knowledge workers") and TRAJAN ("a public-facing AI concierge built to modernize government service delivery"); a "Deployed in government" strip of 15 agency logos; "FedRAMP Ready in AWS GovCloud (US)"; no statistics, testimonials or case studies.Source
  • 11

    Two legislative bodies already use Vulcan (the North Carolina General Assembly and Idaho's Legislative Services Office), and the government site has pages for bill tracking, fiscal notes and the legislature. But nothing is packaged around the session calendar, when legislative staff need 50-state comparisons, fiscal notes and bill analysis fastest.

    Medium impactMedium effort First result in 1 quarter Deployed Agent Orchestrator

    First action

    Ask the two legislative customers which tasks peak during session.

    How to measure it

    Legislative briefings booked

    Now
    –
    Target
    10
    By
    90 days

    Steps

    1. 1

      Interview customers

      Session-time tasks and pain.

      Deployed Agent Orchestrator 1 week

    2. 2

      Define the package

      Scope, training and price.

      Co-Founder & CEO 1 week

    3. 3

      Update the page

      Legislature page section and briefing.

      Agent Orchestrator 3 days

    4. 4

      Get a quote

      From a legislative customer.

      Deployed Agent Orchestrator 2 weeks

    5. 5

      Reach out

      Legislative service agencies and fiscal offices.

      SDR / BDR 4 weeks

    6. 6

      Train before session

      Staff training for new customers.

      Deployed Agent Orchestrator ongoing

    First result
    1 quarter
    Cost
    Staff time
    Owner
    Deployed Agent Orchestrator

    Smallest test

    Offer the package to five legislative service agencies.

    Why it works

    Build a "Session package": a fixed-scope offer for nonpartisan legislative staff and fiscal offices. It includes bill tracking, a 50-state comparison on request, fiscal-note drafting support with every source cited, and training for staff before session. Add a legislature page section and a short briefing aimed at legislative service agencies. Ask the two legislative customers for a quote on session-time use. Offer it through their peer network events.

    Legislative staff have a hard deadline and a short window. A packaged offer that matches the calendar is easier to approve than an open-ended platform.

    Risks and how to handle them

    • Legislatures are cautious about partisan perception

      Sell to nonpartisan staff offices and stress citation-only, neutral analysis.

    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 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
    • Your websiteJustinian page: "1 agent becomes 50" (50-state research that cites every statute to its source and keeps watch on changes), permitting, Vulcan Office, and app building inside the agency boundary; available on the web, macOS and Windows apps, Slack, Teams and email; a "Request Briefing" form; no pricing and no customer proof.Source
  • 12

    TREO.Texas.gov is Vulcan's flagship public proof: "The nation's first government AI concierge for citizens", spanning 50 agencies and 1,427 workflows, and covered by StateScoop. The site shows its scope, not its use. Every other state evaluating Trajan wants to know whether citizens actually use it and whether agency staff save time.

    High impactMedium effort First result in 1 quarter Deployed Agent Orchestrator

    First action

    Propose the scorecard metrics to the Texas office.

    How to measure it

    Trajan briefing requests

    Now
    –
    Target
    +40%
    By
    2 quarters

    Steps

    1. 1

      Agree metrics

      With the Texas office, privacy-safe and aggregate.

      Deployed Agent Orchestrator 2 weeks

    2. 2

      Build the report

      Automated quarterly numbers.

      Agent Orchestrator 2 weeks

    3. 3

      Approve

      Texas reviews the first edition.

      Deployed Agent Orchestrator 2 weeks

    4. 4

      Publish

      On the Trajan page.

      Agent Orchestrator 1 day

    5. 5

      Pitch

      Government-technology press.

      Marketing lead 2 weeks

    6. 6

      Use in sales

      In every Trajan briefing.

      SDR / BDR ongoing

    First result
    1 quarter
    Cost
    Staff time
    Owner
    Deployed Agent Orchestrator

    Smallest test

    Share one month's aggregate numbers with the next Trajan prospect, with Texas's consent.

    Why it works

    Agree with the Texas office on a short public scorecard, published each quarter: conversations, top questions, permits and licences started, share answered without staff, languages used and citizen satisfaction. Put it on the Trajan page and in Texas's own announcements. Use it in every Trajan briefing, and pitch the first edition to government-technology press.

    Usage numbers from a live state service are the most persuasive proof for other states. Publishing jointly gives Texas credit and Vulcan a recurring news moment.

    Risks and how to handle them

    • Texas declines to publish

      Offer a private version for reference calls and publish only scope numbers.

    Evidence

    • 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 websiteMedia Coverage page: StateScoop, May 15, 2026, "Vulcan partners with Texas, delivering AI to help public navigate regulations, permits, and licenses"; Fortune, September 16, 2025; a $10.9M seed round announced October 9, 2025 (General Catalyst, AP, Axios Pro, Law360, Austin Business Journal). The page lists headlines and dates only.Source
  • 13

    Justinian's headline skill is "1 agent becomes 50": a 50-state survey with every statute cited. Commercial visitors (law firms, compliance teams, startups) cannot see one. There is no pricing, trial or sample on the commercial pages, only "Book a briefing". Quorum, by contrast, shows 2,000+ policy teams and public ratings. A lawyer who could see one real cited survey would understand the product in a minute.

    High impactMedium effort First result in 1 month Co Founder & CTO

    First action

    Publish five sample surveys from questions customers have already asked (with permission).

    How to measure it

    Sample-to-briefing rate

    Now
    –
    Target
    15%
    By
    90 days

    Steps

    1. 1

      Pick questions

      20 common commercial 50-state questions.

      Co-Founder & CEO 2 days

    2. 2

      Run and review

      Generate and check every citation.

      Agent Orchestrator 2 weeks

    3. 3

      Publish library

      Dated, cited, linked from commercial paths.

      Agent Orchestrator 3 days

    4. 4

      Build the request

      One question per organisation, delivered by email.

      Co-Founder & CTO 2 weeks

    5. 5

      Route leads

      Every request to the SDR with the question.

      SDR / BDR ongoing

    6. 6

      Measure

      Requests, briefings and closes.

      Co-Founder & CEO monthly

    First result
    1 month
    Cost
    Compute and review time
    Owner
    Co Founder & CTO

    Smallest test

    Publish three sample surveys on the law-firm page.

    Why it works

    Publish a library of 20 sample 50-state surveys on common commercial questions (licensing for a type of business, data breach notice rules, non-compete limits), each with full citations and a date. Add "Ask one 50-state question": a visitor enters a question and a work email, Vulcan runs it, and the cited survey arrives by email with a briefing link. Cap it at one per organisation and review outputs at first.

    Showing the output is the shortest path to belief for a sceptical legal buyer. The samples also rank in search for questions lawyers actually ask, and each request is a qualified lead with a stated need.

    Risks and how to handle them

    • An error in a public sample

      Human review before publishing, dates on every survey and a clear note that it is not legal advice.

    Evidence

    • Your websiteCommercial page: "For teams that have to get it right."; six paths (law firms, regulatory and compliance, policy, trade associations, in-house counsel, startups); "157,000,000,000 records across 141 source families"; no pricing, trial or self-serve sign-up, and no logos or testimonials; every path, including startups, ends in "Book a briefing".Source
    • Your websiteJustinian page: "1 agent becomes 50" (50-state research that cites every statute to its source and keeps watch on changes), permitting, Vulcan Office, and app building inside the agency boundary; available on the web, macOS and Windows apps, Slack, Teams and email; a "Request Briefing" form; no pricing and no customer proof.Source
    • Competitor researchQuorum's homepage: "AI For Your Government Affairs Team"; "Trusted by 2,000+ Policy Teams Nationwide"; a G2 rating of 4.3 from 180 reviews; claims of 10+ hours saved per customer per week; named AI agents for bill tracking and meeting prep.Source
  • 14

    The corpus is Vulcan's moat (157 billion records, 141 source families, 15 categories), and every source already has its own page. But only some entries give a record count and only some show a date range, so a researcher cannot tell how complete or current a source is. These pages could rank for searches on the underlying public datasets, where analysts and lawyers start.

    Medium impactMedium effort First result in 2 months Agent Orchestrator

    First action

    Pull live counts and refresh dates for all 141 sources.

    How to measure it

    Corpus page organic traffic

    Now
    –
    Target
    3x
    By
    2 quarters

    Steps

    1. 1

      Pull data

      Counts, years and refresh dates per source.

      Agent Orchestrator 3 days

    2. 2

      Template

      One standard block per corpus page.

      Agent Orchestrator 2 days

    3. 3

      Example questions

      Two per source, with answers.

      Agent Orchestrator 2 weeks

    4. 4

      Automate

      Counts and dates refresh from the database.

      Co-Founder & CTO 1 week

    5. 5

      Add CTAs

      Briefing link on each page.

      Agent Orchestrator 1 day

    6. 6

      Measure

      Search traffic and briefings by source.

      Marketing lead monthly

    First result
    2 months
    Cost
    Engineering time
    Owner
    Agent Orchestrator

    Smallest test

    Complete the 27 legal source pages first.

    Why it works

    Add the same block to every corpus page: what the source is, record count, coverage years, update frequency, last refreshed date, and two example questions Justinian answers from it, with the answer shown. Add a "Use this source in a briefing" link. Generate the counts and dates automatically from the live database so they never go stale.

    Precise, current coverage data builds trust with researchers and search engines alike, and example questions show the value of each source.

    Risks and how to handle them

    • Exposing non-public customer data

      Show only public sources; leave customer-ingested data off the pages.

    Evidence

    • Your websiteCorpus page: "157,000,000,000 records. One corpus."; 141 source families in 15 categories and 51 jurisdictions; each source has its own page, but only some entries give record counts and only some show a date range; a "Missing something? Tell us what to add" link to a data request form.Source
    • Your websiteCommercial page: "For teams that have to get it right."; six paths (law firms, regulatory and compliance, policy, trade associations, in-house counsel, startups); "157,000,000,000 records across 141 source families"; no pricing, trial or self-serve sign-up, and no logos or testimonials; every path, including startups, ends in "Book a briefing".Source
  • 16

    Justinian's work leaves the building every day: memos, redlines, comment responses and surveys go to legislators, other agencies, clients and opposing counsel. Since 3.1.0 it also drafts replies inside users' own mail. Every claim is cited, but the reader at the other end cannot see the citations working and never meets the product.

    Medium impactMedium effort First result in 2 months Co Founder & CTO

    First action

    Prototype the verify page for 50-state surveys, which use only public sources.

    How to measure it

    Verify-page referrals

    Now
    –
    Target
    5 a month
    By
    2 quarters

    Steps

    1. 1

      Scope

      Public-source outputs only; admin controls.

      Co-Founder & CTO 3 days

    2. 2

      Build the page

      Claim, passage, date, read-only.

      Agent Orchestrator 2 weeks

    3. 3

      Security review

      No customer data, expiring links.

      Security and compliance lead 1 week

    4. 4

      Pilot

      Commercial customers first.

      Deployed Agent Orchestrator 3 weeks

    5. 5

      Add the footer

      Briefing link on each verify page.

      Agent Orchestrator 1 day

    6. 6

      Track

      Clicks and briefings by referring organisation.

      SDR / BDR monthly

    First result
    2 months
    Cost
    Engineering time
    Owner
    Co Founder & CTO

    Smallest test

    Add verify links to sample surveys (idea 13) first.

    Why it works

    Add an optional "verify" link to exported documents. It opens a read-only page listing each claim with its source passage (only public sources, never customer data), and the date it was checked. At the bottom is a short line: "Researched with Justinian. Request a briefing." Admins can turn it on or off per organisation. Track which organisations' readers click through.

    Readers who can check a citation in one click trust the document more, which makes users look good. Each document becomes a quiet demo to exactly the kind of people who buy, inside government and in law firms.

    Risks and how to handle them

    • Agencies object to vendor branding on official work

      Off by default for government; brand only the verify page, never the document.

    Builds on

    Evidence

    • Your websiteJustinian page: "1 agent becomes 50" (50-state research that cites every statute to its source and keeps watch on changes), permitting, Vulcan Office, and app building inside the agency boundary; available on the web, macOS and Windows apps, Slack, Teams and email; a "Request Briefing" form; no pricing and no customer proof.Source
    • Your websiteJustinian 3.1.0 (November 2026): Mail (connects Gmail or Outlook, drafts replies, and each send needs an approval card; users can also forward or CC threads to a Justinian address), GIS (shapefiles, geodatabases, KML; spatial questions such as which parcels fall in a flood zone) and a browser CAD editor for DXF and DWG files.Source
    • Your websiteJustinian 2.1.9 release note (July 2026): "We benchmarked 50-state surveys against Lexis, Westlaw" and four general-purpose AI assistants; "Justinian won on both speed and accuracy." No method, test set or numbers are published.Source
  • 17

    Vulcan is hiring a Deployed Agent Orchestrator with weekly travel, so deployments are hands-on and on site. The briefing agenda already includes pilot scoping. Without success measures agreed up front, pilots drift, renewals depend on goodwill, and no case study comes out, which is why the Deployments page has 50 names and no results.

    High impactLow effort First result in 2 months Deployed Agent Orchestrator

    First action

    Draft the scorecard and use it on the next pilot.

    How to measure it

    Pilots converted

    Now
    –
    Target
    75%
    By
    2 quarters

    Steps

    1. 1

      Draft the scorecard

      Workflows, baselines, targets, decision date.

      Deployed Agent Orchestrator 2 days

    2. 2

      Agree in week one

      Sponsor signs off.

      Deployed Agent Orchestrator 1 week

    3. 3

      Measure weekly

      Usage and outcome numbers.

      Deployed Agent Orchestrator weekly

    4. 4

      Midpoint review

      With the sponsor.

      Deployed Agent Orchestrator 1 day

    5. 5

      Results memo

      Doubles as case study draft and expansion proposal.

      Deployed Agent Orchestrator 3 days

    6. 6

      Decide

      Expand, extend or stop.

      Co-Founder & CEO 1 day

    First result
    2 months
    Cost
    $0
    Owner
    Deployed Agent Orchestrator

    Smallest test

    Retrofit the scorecard to one current pilot.

    Why it works

    Create a one-page pilot scorecard signed off by the agency sponsor in week one: 3 workflows, a baseline for each (hours per task, turnaround, backlog), target numbers, and the decision at day 30-60 (expand, extend or stop). Measure weekly, review with the sponsor at the midpoint, and finish with a results memo that doubles as the draft case study and the expansion proposal.

    Agreed measures turn a pilot into a decision, give the sponsor evidence to take to leadership, and feed the proof pages (idea 1) automatically.

    Risks and how to handle them

    • Baselines are hard to measure in agencies

      Use simple time-on-task samples from five staff.

    Evidence

    • HiringCareers page (checked November 9, 2026): four open roles, all in Austin, TX: Agent Orchestrator (Engineering), Deployed Agent Orchestrator (Engineering / GTM, weekly travel), SDR / BDR (GTM) and Executive Assistant (Operations); titles only, no role descriptions; the page says "Build the infrastructure for AGI-era government and law."Source
    • Your websiteState agencies briefing page: "Your statutes, your regulations, and the federal authority they implement — one corpus."; the agenda covers a live walkthrough on the agency's own rules, a monitoring demo, a comparison with other states, and deployment, security posture and pilot scoping; the form asks for focus areas (Justinian or Trajan); no customer proof.Source
    • 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
  • 18

    Trade associations are one of Vulcan's six commercial paths. They spend much of their time tracking how rules differ by state for their members, which is exactly Justinian's 50-state survey. An association that sends its members a cited 50-state update reaches hundreds of companies at once.

    Medium impactMedium effort First result in 1 quarter Co Founder & CEO

    First action

    Shortlist five associations whose members face heavy state-by-state rules.

    How to measure it

    Association-sourced briefings

    Now
    –
    Target
    15
    By
    2 quarters

    Steps

    1. 1

      Shortlist

      Five associations in heavily regulated industries.

      Co-Founder & CEO 2 days

    2. 2

      Pitch

      A free first edition.

      SDR / BDR 3 weeks

    3. 3

      Produce

      Co-branded 50-state update.

      Agent Orchestrator 2 weeks

    4. 4

      Review

      Association policy staff check it.

      Co-Founder & CEO 1 week

    5. 5

      Distribute

      Through the association's member channels.

      Co-Founder & CEO 1 week

    6. 6

      Follow up

      Member briefings.

      SDR / BDR ongoing

    First result
    1 quarter
    Cost
    Staff time; partner discounts
    Owner
    Co Founder & CEO

    Smallest test

    Produce one free 50-state update for one association.

    Why it works

    Offer two or three associations a pilot: a quarterly co-branded 50-state regulatory update for their industry (licensing, reporting, product rules), produced with Justinian and reviewed by the association's policy staff. Members who want their own questions answered get a briefing. The association gets a member benefit at a discount; Vulcan gets a trusted channel to many companies. Add a trade association case study once the first one runs.

    Associations are trusted, already collect member questions, and need regular content. One partner reaches a whole industry's compliance and policy teams.

    Risks and how to handle them

    • Associations want exclusivity

      Offer exclusivity by industry for a limited period only.

    Evidence

    • Your websiteCommercial page: "For teams that have to get it right."; six paths (law firms, regulatory and compliance, policy, trade associations, in-house counsel, startups); "157,000,000,000 records across 141 source families"; no pricing, trial or self-serve sign-up, and no logos or testimonials; every path, including startups, ends in "Book a briefing".Source
    • Your websiteJustinian page: "1 agent becomes 50" (50-state research that cites every statute to its source and keeps watch on changes), permitting, Vulcan Office, and app building inside the agency boundary; available on the web, macOS and Windows apps, Slack, Teams and email; a "Request Briefing" form; no pricing and no customer proof.Source
    • Competitor researchQuorum's homepage: "AI For Your Government Affairs Team"; "Trusted by 2,000+ Policy Teams Nationwide"; a G2 rating of 4.3 from 180 reviews; claims of 10+ hours saved per customer per week; named AI agents for bill tracking and meeting prep.Source

Big bets 3

Larger plays that can change the trajectory.

  • 19

    The startups page promises to map licensing, filing obligations and state expansion, yet it ends in the same enterprise "Book a briefing" as a statewide deployment. The iOS app is usable only with an active Vulcan agreement. Small firms and startups rarely book enterprise briefings, but they do pay for tools they can start using the same day.

    High impactHigh effort First result in 2 quarters Co Founder & CEO

    First action

    Count sample requests from organisations under 50 people.

    How to measure it

    Self-serve paying teams

    Now
    –
    Target
    100
    By
    2 quarters after launch

    Steps

    1. 1

      Size demand

      Small-team sample requests and briefing no-shows.

      Co-Founder & CEO 1 month

    2. 2

      Define the plan

      Seats, allowance, limits.

      Co-Founder & CEO 2 weeks

    3. 3

      Build sign-up

      Payment, provisioning and onboarding.

      Co-Founder & CTO 6 weeks

    4. 4

      Security baseline

      Standard terms for small accounts.

      Security and compliance lead 2 weeks

    5. 5

      Price test

      Two price points.

      Co-Founder & CEO 1 month

    6. 6

      Onboarding

      First survey within ten minutes.

      Agent Orchestrator 2 weeks

    7. 7

      Upgrade path

      Usage alerts route to the SDR.

      SDR / BDR ongoing

    First result
    2 quarters
    Cost
    Engineering time and compute
    Owner
    Co Founder & CEO

    Smallest test

    Offer a paid pilot link to the next 20 small-team sample requesters.

    Why it works

    Once the public sample (idea 13) shows how many small teams ask, launch a self-serve plan: a few seats, a monthly survey and research allowance, cited exports, and standard security. Card payment, instant access, and an upgrade path to the enterprise agreement. Keep government sales-led. Price against the time a 50-state survey costs a junior associate, and test two price points.

    It opens a market the sales team cannot reach economically, creates product-led referrals into larger firms, and gives the commercial pages a clear next step.

    Risks and how to handle them

    • Support load from small accounts

      In-product help and email-only support.

    • Cannibalising enterprise deals

      Seat caps and enterprise-only features (private deployment, SSO).

    Builds on

    Evidence

    • Your websiteCommercial page: "For teams that have to get it right."; six paths (law firms, regulatory and compliance, policy, trade associations, in-house counsel, startups); "157,000,000,000 records across 141 source families"; no pricing, trial or self-serve sign-up, and no logos or testimonials; every path, including startups, ends in "Book a briefing".Source
    • App StoreJustinian iOS app (Vulcan Technologies, Inc.): 5.0 from 6 ratings; free, but usable only by organizations with an active Vulcan agreement, with access provisioned by the organization's administrator; version 2.6.5 updated November 2026.Source
    • Competitor researchQuorum's homepage: "AI For Your Government Affairs Team"; "Trusted by 2,000+ Policy Teams Nationwide"; a G2 rating of 4.3 from 180 reviews; claims of 10+ hours saved per customer per week; named AI agents for bill tracking and meeting prep.Source
  • 20

    VulcanGov is FedRAMP Ready and listed on the Marketplace. Its boundary is architected to the Rev. 5 baseline (about 325 controls) and assessed by an accredited 3PAO. But the FedRAMP page names no sponsor, timeline or federal customer, and the security page says Vulcan is still pursuing full authorization. The federal agency page sells "FedRAMP Ready, inside the GovCloud boundary" to buyers who usually need an authorization to operate.

    High impactHigh effort First result in 2 quarters Security and compliance lead

    First action

    List the three federal agencies with the most regulatory-review work, and any existing contacts there.

    How to measure it

    Authorization milestones

    Now
    –
    Target
    Sponsor signed
    By
    2 quarters

    Steps

    1. 1

      Shortlist agencies

      Mission fit and existing contacts.

      Co-Founder & CEO 2 weeks

    2. 2

      Design the pilot

      A focused federal use case.

      Deployed Agent Orchestrator 1 month

    3. 3

      Secure sponsor

      Agency agrees to sponsor authorization.

      Co-Founder & CEO 1 quarter

    4. 4

      Close gaps

      Remaining controls and documents.

      Security and compliance lead 1 quarter

    5. 5

      Assessment

      3PAO full assessment.

      Security and compliance lead 1 quarter

    6. 6

      Publish progress

      Milestones on the FedRAMP page.

      Agent Orchestrator ongoing

    First result
    2 quarters
    Cost
    Significant assessment and staff cost
    Owner
    Security and compliance lead

    Smallest test

    Run one federal briefing using the existing FedRAMP Ready package.

    Why it works

    Pick a federal agency whose mission overlaps Vulcan's strongest workflows (regulatory review, grants, enforcement records) and offer a focused pilot that leads to agency sponsorship of the authorization. Use the state deployments and the benchmark as proof. Budget the remaining assessment work, then publish progress on the FedRAMP page (sponsor secured, assessment, authorization).

    Full authorization unlocks federal buyers and is also a strong trust signal for states and large law firms. A sponsor with a real use case is the fastest path.

    Risks and how to handle them

    • Long federal timelines drain a small team

      Pursue it only with a committed sponsor; keep state work the priority.

    Builds on

    Evidence

    • Your websiteFedRAMP page: VulcanGov is "designated FedRAMP Ready", architected to the Rev. 5 baseline ("roughly 325 controls across 17 families") and assessed by an accredited 3PAO; no sponsor, timeline or federal customer is named; CTAs include "Request a security briefing".Source
    • Your websiteSecurity page: "Vulcan is FedRAMP® Ready", listed on the FedRAMP Marketplace "as we pursue full authorization"; SOC 2 report and ISO 27001 certificate available by request; TX-RAMP described as "Aligned to Texas state agency security requirements for public-sector deployments". The commercial page lists SOC 2, ISO 27001, TX-RAMP and private deployment side by side, and the state agencies briefing page offers a "TX-RAMP / FedRAMP posture" discussion.Source
  • 21

    Vulcan holds statutes, regulations and registers for all 50 states plus DC, and its red tape workflow already counts restrictions and finds provisions with no live enabling authority. Its origin story is a state using that analysis on its own code. No one publishes a neutral, comparable count of every state's regulatory code with a method anyone can check.

    High impactHigh effort First result in 2 quarters Co Founder & CEO

    First action

    Run the restriction count for five states to test the method.

    How to measure it

    Index-sourced briefings

    Now
    –
    Target
    25
    By
    60 days after launch

    Steps

    1. 1

      Design the method

      Measures, definitions and limits.

      Co-Founder & CTO 1 month

    2. 2

      Outside review

      Academic reviewers check the method.

      Co-Founder & CEO 1 month

    3. 3

      Run 51 jurisdictions

      With spot checks per state.

      Agent Orchestrator 1 month

    4. 4

      Build pages

      One page per state, with data download.

      Agent Orchestrator 3 weeks

    5. 5

      Brief agencies

      Private previews for customers.

      Deployed Agent Orchestrator 2 weeks

    6. 6

      Launch

      State-by-state press outreach.

      Marketing lead 1 month

    7. 7

      Follow up

      Briefing offers to every regulatory office.

      SDR / BDR ongoing

    First result
    2 quarters
    Cost
    Staff time and reviewer fees
    Owner
    Co Founder & CEO

    Smallest test

    Publish a five-state pilot with method notes.

    Why it works

    Publish a yearly index: for each state, the size of the administrative code, restrictive terms per thousand words, share of provisions with no traceable statutory authority, and change over the year. Release the method and data, give each state a page, and offer agencies a free private briefing on their own results. Keep it strictly descriptive and nonpartisan, and have outside academics review the method.

    A credible annual index earns press in every state, becomes the reference buyers cite, and gives every regulatory office a reason to talk to Vulcan about its own numbers.

    Risks and how to handle them

    • Seen as political

      Descriptive measures only, no rankings of policy quality, outside review.

    • Customers dislike their scores

      Private previews and the right to add context.

    Builds on

    Evidence

    • Your websiteCorpus page: "157,000,000,000 records. One corpus."; 141 source families in 15 categories and 51 jurisdictions; each source has its own page, but only some entries give record counts and only some show a date range; a "Missing something? Tell us what to add" link to a data request form.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
    • Press coverageRoute Fifty (August 22, 2025): Virginia's governor signed a July 2025 executive order saying the commonwealth "must use" agentic AI to streamline its regulations; Vulcan built a central database of Virginia's regulations, statutes and case law whose agents flag discrepancies, such as a fine enforced above the statutory amount under a repealed rule; Vulcan was incorporated in April 2025 and won the contract in May.Source
    • Your websiteMedia Coverage page: StateScoop, May 15, 2026, "Vulcan partners with Texas, delivering AI to help public navigate regulations, permits, and licenses"; Fortune, September 16, 2025; a $10.9M seed round announced October 9, 2025 (General Catalyst, AP, Axios Pro, Law360, Austin Business Journal). The page lists headlines and dates only.Source

Wildcards 1

Unexpected experiments, each with a cheap way to test it.

  • 22

    Vulcan's users sit in similar jobs across about a dozen states: environmental regulators in Oklahoma and Louisiana, Medicaid and health staff in Mississippi, governors' offices in four states, and legislative staff in two. The state briefing even offers a "comparison with other states". These users rarely meet, so a workflow that works in one state stays there.

    Medium impactMedium effort First result in 1 quarter Deployed Agent Orchestrator

    First action

    Invite the environmental agency users to the first roundtable.

    How to measure it

    Weekly active users per agency

    Now
    –
    Target
    +25%
    By
    2 quarters

    Steps

    1. 1

      Pick the first group

      Environmental and regulatory staff.

      Deployed Agent Orchestrator 1 week

    2. 2

      Invite

      Through each sponsor.

      Deployed Agent Orchestrator 2 weeks

    3. 3

      Run the roundtable

      One agency shows a workflow and result.

      Deployed Agent Orchestrator 1 day

    4. 4

      Share workflows

      Opt-in library of saved workflows.

      Agent Orchestrator 1 month

    5. 5

      Expand groups

      Health, legislative, governors' offices.

      Deployed Agent Orchestrator 1 quarter

    6. 6

      Annual day

      In person in Austin.

      Co-Founder & CEO yearly

    First result
    1 quarter
    Cost
    Staff time; event costs
    Owner
    Deployed Agent Orchestrator

    Smallest test

    One 45-minute roundtable with three agencies.

    Why it works

    Start a closed, invite-only network for customer staff: a quarterly virtual roundtable by agency type (regulatory, environment, health, legislative), a shared library of saved Justinian workflows that agencies choose to share, and an annual in-person day in Austin. Each session features one agency showing a workflow and its result. Customer staff own the agenda; Vulcan hosts.

    Peers learning from peers drives adoption and renewals, surfaces case studies, and makes switching away costly because the network itself has value.

    Risks and how to handle them

    • Agencies cannot share internal work

      Share methods and templates, never documents or data.

    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 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
    • Your websiteState agencies briefing page: "Your statutes, your regulations, and the federal authority they implement — one corpus."; the agenda covers a live walkthrough on the agency's own rules, a monitoring demo, a comparison with other states, and deployment, security posture and pilot scoping; the form asks for focus areas (Justinian or Trajan); no customer proof.Source
More example playbooks and reviews

More growth playbooks

Other companies we have researched, each read from what they are hiring for.

  • vCluster Labs growth strategyA platform that lets AI cloud providers, AI factories and enterprises turn GPU and CPU infrastructure into isolated tenant clusters…22 growth ideas
  • SanterMedia growth strategyA gym marketing agency: Meta ads, lead-nurture systems and sales coaching (the "Local Hero" campaigns and a "Serve First" sales process)…21 growth ideas
  • VoiceOS growth strategyA voice assistant for Mac and Windows from WakoAI, Inc. It handles dictation that cleans up speech into finished text, and Agent Mode…22 growth ideas
  • WorkManagement.Tools growth strategyA small remote team led by a former ClickUp product thinker that builds automated order entry: emailed and PDF purchase orders read into…23 growth ideas
  • Take-Two Interactive growth strategyA video game developer and publisher whose labels include Rockstar Games, 2K, Zynga and Ghost Story Games; take2games.com is its…21 growth ideas
  • Daily Dump growth strategyA Bengaluru design company that makes home and community composters (terracotta Khamba, Gobble, Gobble Mini and Max, bulk converters)…21 growth ideas
  • Dr. Jose Barrera, MD Plastic Surgery and MedSpa growth strategyA San Antonio facial plastic and reconstructive surgery practice led by a triple board-certified surgeon (ENT, sleep medicine, facial…24 growth ideas
  • Leeroo growth strategyUniforge, an enterprise AI platform that connects to a company's systems (CRM, ERP, billing, ITSM, support, HR), learns them into one…23 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on November 9, 2026, and cites them throughout. Vulcan Technologies did not commission, review or endorse it, and Programmable is not affiliated with Vulcan Technologies. Company and product names are trademarks of their owners, used only to identify them. The ideas are suggestions and opinion, not professional, legal or financial advice, and not statements about how Vulcan Technologies runs its business.

Something wrong, or do you represent Vulcan Technologies? Email [email protected] and we will correct it or take it down.

30/60/90 roadmap

What to focus on in each month, and the ideas that carry it.

  1. Days 1 to 307 ideas

    Proof on the pages buyers read: deployment stories, press in context, consistent security wording, homepage description, accessibility fixes, the release-notes feed and data-request leads.

  2. Days 31 to 6011 ideas

    Sales engine: a How to buy page, trigger-based outbound, statewide expansion, the legislative package, the TREO scorecard, the public 50-state sample, corpus pages, share links, pilot scorecards, trade associations and the benchmark method.

  3. Days 61 to 904 ideas

    Commit to the big bets: a priced starter plan, full FedRAMP authorization through a federal sponsor, an annual State Red Tape Index and a peer network of agency users.

The research behind the plan

3 research areas, each summarised in a few lines. Open any of them for the full detail.

Customers

What customers say

Customers value answers cited to the exact statute, rule or case. The most cited problem: regulatory reduction mandates with small rule-review teams.

  • 50-state surveys in one pass
  • Permitting and licensing backlogs and citizen confusion
  • In their words: “red tape”

Market

Competitive landscape

4 competitors compared: Polimorphic, Quorum, Lexis and Westlaw and Large consultancies.

  • Gap to exploit: Agency-grade AI that ties every answer to statutory authority
  • Polimorphic: Service-desk focus, without a deep legal and regulatory corpus
  • Quorum: Built for tracking and advocacy, not for agencies' own rule review

Hiring signals

Vulcan is hiring small and pointed, all in Austin: an SDR / BDR, which means outbound to agencies is starting (ideas 9, 15).

  • SDR / BDR: Outbound sales is starting. Ideas 9, 15.
  • Deployed Agent Orchestrator: On-site deployments with weekly travel. Ideas 10, 12, 17, 22.
  • Agent Orchestrator: Engineering capacity for agents, site and corpus. Ideas 3, 7, 14.

From the team that wrote this playbook

All products
  • ProgrammableAgencyWorking AI systems in days, not quarters (opens programmable.agency in a new tab)
  • ProgrammableInfoAn agent that finds, researches and asks firstNew accounts get 100,000 free enrichment credits with code BETA100K (opens programmable.info in a new tab)
  • ProgrammableDigitalScreenshots in, an animated product demo out (opens programmable.digital in a new tab)
  • ProgrammableWatchKnow the day a supplier falls out of compliance (opens programmable.watch in a new tab)
  • ProgrammableTalkGet registrants for your events, and know who’s coming (opens programmable.talk in a new tab)
  • ProgrammableMediaAn AI note taker, interpreter and webinar host for your calls (opens programmable.media in a new tab)
  • ProgrammablePageText what you need, your customer gets a page that works (opens programmable.page in a new tab)
  • ProgrammableCommunityForums with labelled AI members, never empty (opens programmable.community in a new tab)
ProgrammableMarketing
ExamplesLeaderboardsProductsTermsPrivacyCookiesDPALegalContact

© 2026 AI-Powered Growth Intelligence