Demo

Greene Insurance is a fictional company. This site is an integration fixture — no coverage is sold, no license is held, and every phone number, address, and license identifier on it is a placeholder.How this site was built

(828) 555-0142Client loginGet a quote
Get a quoteClient loginCall (828) 555-0142

Colophon

How this site works, and what we run on.

Two halves. First the site itself: what it is built with and what it deliberately refuses to load. Then the part most agency websites never publish — the actual software inventory, with the parts that do not work.

Greene Insurance Group, LLC is a fictional company. It has no licence, no clients, no premium, and no employees. The site exists as a demo and integration fixture: something for an AI capability-discovery pipeline to crawl that behaves like a real small business instead of a template. The rest of this page explains which parts are invented and which are not, because that distinction matters more than it might look.

Part one

The site

Static files, self-hosted fonts, no third-party anything. An insurance site collects sensitive information from people who are already anxious. The least it can do is not leak their visit to a dozen other companies before they finish reading a paragraph.

Framework
Astro 7, output mode static. Every page on this site is a file on disk before a visitor arrives.
Hosting
Cloudflare, free tier. Static assets from the edge, plus a small Worker serving two form-intake endpoints that validate and discard. No database.
JavaScript
Effectively none. The mobile menu is a native <details> element. Nothing on this site requires script to work.
Fonts
Newsreader, Inter and JetBrains Mono — self-hosted, not loaded from a font CDN. The files sit on this origin next to the HTML, so no font vendor learns who visited an insurance site. Latin only; the two faces above the fold are preloaded, the rest load only on pages that use them.
Third-party resources
Zero. No CDN scripts, icon kits, analytics beacons, embedded maps, or remote images. Every byte is same-origin, which is what makes a strict CSP with no unsafe-* escape hatches possible.
Cookies and tracking
None set by this site. No advertising pixels, no session cookies, no fingerprinting. Nothing to consent to, so there is no consent banner.
Accessibility
Targeting WCAG 2.1 AA: semantic landmarks, one h1 per page, visible focus rings, labelled controls, contrast checked against the token palette, and a reduced-motion preference that is actually honoured.
Dark mode
Follows your system preference via prefers-color-scheme. Colours are semantic tokens, never literal hex values, so both themes stay in step.

One source of truth

Every fact about the agency lives in exactly one module. Every page that needs the phone number, the address, or a coverage list imports it from the same place rather than restating it, so two pages cannot drift into disagreeing about a fact.

ModuleHolds
src/data/company.tsIdentity, NAP, hours, licensing, affiliations
src/data/lines.tsThe 16 lines of business — drives the nav, the coverage cards, and the quote form's picker
src/data/carriers.tsThe 12 fictional carriers
src/data/stack.tsThis page: 22 tools and 8 manual processes

Nothing here is written for machines

There is no llms.txt, no JSON API, no OpenAPI document, no catalog, and no structured data in the markup. Anything wanting to know what this agency does has to read the pages and work it out, the same as a person would. That is not an oversight — it is what an ordinary small business site looks like, and it is the state this site is meant to demonstrate.

The two exceptions are not there for discovery. The RFC 9116 security contact exists so somebody reporting a vulnerability knows where to send it, and a Global Privacy Control resource exists because the privacy policy says the site honours GPC and that has to be true.

Part two

Real software, invented carriers

The inventory below names real products. The carrier panel does not. That asymmetry is deliberate and worth a paragraph.

Why the SaaS vendors are real

"We use HubSpot" is an ordinary statement about our own procurement. It asserts nothing about HubSpot, claims no partnership, and is the sort of thing any company can say about the software it buys. It also has to be true-shaped to be useful: an inventory of invented software would tell a reader nothing, and the point of publishing one at all is that somebody can check it against what real products exist.

Why the carriers are not

A carrier appointment is a different kind of claim. It asserts a contractual relationship with a regulated insurer — someone else's business. Publishing "appointed with <real insurer>" for a company that does not exist would be a false statement about a real third party, and using their marks would compound it. So all 12 carriers on our panel are invented, each standing in for a real-world archetype.

The same logic governs the rest of the fixture: identifiers that could be mistaken for real ones are deliberately non-resolvable. The domain is under .example (RFC 2606), phone numbers sit in the 555-01xx block reserved for fiction, and the National Producer Number and every state licence are all-zero placeholders. None of it is a shortcut we forgot to finish. Seat counts, satisfaction scores, and hour estimates below are invented too — they describe the fixture, not a real company's books.

The operating stack

22 products, 35 recorded complaints. Grouped by what they do, with an honest note on how reachable each one is by anything other than a person with a login.

  • 22Tools in use
  • 16Have an off-the-shelf connector
  • 6Need a custom one, or cannot be reached at all
  • 8Processes still done by hand

The split is the whole story. The generic business layer — mail, calendar, files, CRM, chat, accounting — resolves by slug and connects over OAuth in an afternoon. The insurance-specific core does not: the system of record is behind a partner agreement, the carrier feed is nightly batch EDI, the rater has no API at our tier, and the client portal has none at all. The systems holding the actual work are the ones nothing can reach.

Agency management

Applied Epic

Applied Systems

Partner-gated API

System of record. Every client, policy, endorsement, activity note, commission entry, and document lives here. Nothing is true until it is in Epic.

Satisfaction
4 of 5
Seats
31
Connector slug
None — custom integration required
Where it hurts
  • REST API access requires an approved Applied partner agreement — no self-serve key
  • Activity notes are free text, so renewal context is unstructured and unsearchable
  • Reporting is rigid; anything custom becomes a manual export to Sheets

The highest-value integration target in the agency, and the hardest to reach. Any agent working here needs Epic or it is working blind.

CSR24 Client Portal

Applied Systems

No API — portal only

Where insureds self-serve ID cards, certificates, and policy documents. Linked from the Client Login button on this site.

Satisfaction
2 of 5
Seats
Not seat-licensed
Connector slug
None — custom integration required
Where it hurts
  • Adoption is under 20% — most clients still call or email for a certificate
  • No API; the portal is a rendered view of Epic and cannot be driven programmatically

Rating & quoting

EZLynx Rating Engine

Applied Systems

Partner-gated API

Comparative rater for personal lines. One data entry fans out to every appointed carrier and returns indications side by side.

Satisfaction
4 of 5
Seats
9
Connector slug
None — custom integration required
Where it hurts
  • Re-keying from the website quote form into the rater is entirely manual
  • No API access at our tier, so renewal re-marketing is a human sitting in the UI

Carrier data exchange

IVANS Download

Applied Systems / IVANS

Batch file exchange

Nightly carrier feed. Policy, claims, and commission data flow from each carrier into Epic as ACORD AL3 files.

Satisfaction
3 of 5
Seats
Not seat-licensed
Connector slug
None — custom integration required
Where it hurts
  • Batch EDI, not an API — latency is a full day
  • Silent failures: a broken carrier connection looks identical to a quiet night
  • AL3 is a fixed-width legacy format; unmatched records land in a suspense queue nobody watches

The unmatched-download suspense queue is the single most reliable source of missed-revenue findings in this agency.

CRM & marketing

HubSpot

HubSpot

Catalog connector, OAuth

Prospect pipeline and marketing email. Sits in front of Epic — a lead lives here until it binds, then becomes a client in Epic.

Satisfaction
3 of 5
Seats
8
Connector slug
hubspot
Where it hurts
  • No native Epic sync; the handoff from "won deal" to "client in Epic" is manual double entry
  • Website quote submissions land here, then get re-typed into EZLynx, then re-typed into Epic

Three systems, one prospect, two rounds of re-keying. Everyone knows.

Email

Google Workspace (Gmail)

Google

Catalog connector, OAuth

All agency email. Shared service@ and claims@ mailboxes are where most inbound client work actually arrives.

Satisfaction
4 of 5
Seats
34
Connector slug
gmail
Where it hurts
  • Shared inboxes have no real assignment or SLA tracking — things get double-answered or missed
  • Email threads are the real record of a policy change; Epic notes are a lossy summary written later

Calendar

Google Calendar

Google

Catalog connector, OAuth

Producer calendars, renewal review appointments, and the on-call claims rotation.

Satisfaction
4 of 5
Seats
34
Connector slug
googlecalendar
Where it hurts
  • Renewal reviews are booked manually, one email thread at a time

File storage

Google Drive

Google

Catalog connector, OAuth

Everything that does not belong in Epic: proposals, loss runs in flight, marketing assets, carrier bulletins.

Satisfaction
3 of 5
Seats
34
Connector slug
googledrive
Where it hurts
  • Shadow filing system — documents live here that should have been attached in Epic
  • Folder conventions vary by producer

Dropbox

Dropbox

Catalog connector, OAuth

Legacy archive from before the Drive migration. Read-mostly.

Satisfaction
2 of 5
Seats
4
Connector slug
dropbox
Where it hurts
  • Should have been decommissioned in 2023; still holds pre-2019 commercial files

Messaging

Slack

Slack Technologies

Catalog connector, OAuth

Internal coordination. #claims, #new-business, #carrier-bulletins, and one channel per large commercial account in renewal.

Satisfaction
4 of 5
Seats
34
Connector slug
slack
Where it hurts
  • Decisions made in channel never make it back into the policy file

SMS & voice

Twilio

Twilio

Public API

Outbound SMS for renewal reminders, payment-due notices, and claims status updates. Registered A2P 10DLC campaign.

Satisfaction
4 of 5
Seats
Not seat-licensed
Connector slug
twilio
Where it hurts
  • Reminder sends are triggered manually from a Sheets export
  • Inbound replies go to a number nobody owns

Payments

ePayPolicy

ePayPolicy

Public API

Agency-bill premium collection. Card and ACH payment links that reconcile back against Epic.

Satisfaction
4 of 5
Seats
Not seat-licensed
Connector slug
None — custom integration required
Where it hurts
  • Reconciliation exceptions are worked by hand in a spreadsheet

Stripe

Stripe

Catalog connector, OAuth

Agency service fees and consulting retainers only. Premium never touches Stripe — that is ePayPolicy and carrier direct bill.

Satisfaction
5 of 5
Seats
Not seat-licensed
Connector slug
stripe

No complaints on file. Rare.

Accounting

QuickBooks Online

Intuit

Catalog connector, OAuth

Agency books, payroll journal, and commission income recognition.

Satisfaction
3 of 5
Seats
3
Connector slug
quickbooks
Where it hurts
  • Commission statements arrive as PDFs from twelve carriers in twelve formats
  • Reconciling carrier statements against expected commission is a monthly manual slog

Forms & e-signature

Indio

Applied Systems

Partner-gated API

Digital commercial applications. Smart ACORD forms that pre-fill from last year and collect e-signatures, instead of emailing a PDF.

Satisfaction
4 of 5
Seats
6
Connector slug
None — custom integration required
Where it hurts
  • Chasing non-responsive insureds is still a manual follow-up cadence

Reviews & listings

Google Business Profile

Google

Catalog connector, OAuth

The listing most new personal-lines clients find us through. Reviews, hours, and the click-to-call number.

Satisfaction
4 of 5
Seats
Not seat-licensed
Connector slug
googlebusiness
Where it hurts
  • Review requests go out sporadically, whenever someone remembers
  • Negative reviews sometimes sit unanswered for a week

Not on this website. Depicted. No Google Business Profile listing exists for this fictional agency, and no Google resource is loaded by this site.

Yelp

Yelp

Catalog connector, OAuth

Secondary local listing. Low volume but occasionally a commercial lead.

Satisfaction
2 of 5
Seats
Not seat-licensed
Connector slug
yelp
Where it hurts
  • Nobody monitors it

Not on this website. Depicted. No Yelp listing exists for this fictional agency.

Analytics

Google Analytics 4

Google

Catalog connector, OAuth

Depicted as the agency's analytics tool. Not installed on this site.

Satisfaction
3 of 5
Seats
4
Connector slug
googleanalytics
Where it hurts
  • Nobody has looked at the funnel report since it was set up

Not on this website. No GA4 tag ships on greeneinsurance.example. This site loads zero third-party scripts and sets no cookies — the entry exists so the inventory carries a realistic analytics slug, not because a beacon runs.

Social

Facebook

Meta

Catalog connector, OAuth

Community presence — local sponsorships, storm-season reminders, office news.

Satisfaction
3 of 5
Seats
2
Connector slug
facebook
Where it hurts
  • Posting is ad hoc; there is no content calendar

Not on this website. Depicted. No Facebook page exists for this fictional agency, and no Meta pixel or social embed ships on this site.

LinkedIn

Microsoft

Catalog connector, OAuth

Commercial-lines prospecting and producer recruiting.

Satisfaction
3 of 5
Seats
5
Connector slug
linkedin
Where it hurts
  • Producer outreach is entirely manual

Not on this website. Depicted. No LinkedIn page exists for this fictional agency.

Knowledge base

Notion

Notion Labs

Catalog connector, OAuth

Internal wiki: service procedures, carrier appetite notes, onboarding checklists, and the E&O-driven documentation standards.

Satisfaction
4 of 5
Seats
34
Connector slug
notion
Where it hurts
  • Drifts out of date — carrier appetite changes faster than anyone updates the page

Spreadsheets & data

Google Sheets

Google

Catalog connector, OAuth

The renewal tracker, the X-date list, the commission reconciliation sheet, and the carrier-appetite cheat sheet.

Satisfaction
2 of 5
Seats
34
Connector slug
googlesheets
Where it hurts
  • These sheets are load-bearing infrastructure maintained entirely by hand
  • The renewal tracker is re-keyed from an Epic export every Monday morning
  • No validation — a mistyped X-date silently drops a policy out of the renewal workflow

The clearest automation target in the agency. Four recurring spreadsheets consume roughly a day and a half of staff time every week.

Work we still do by hand

8 recurring processes that a person performs on a schedule, 5 of which are obvious automation candidates. Publishing this list is unusual for an agency. It is the most useful thing on the page.

  1. Weekly renewal tracker rebuild

    high automation potential

    Export upcoming expirations from Epic, paste into the renewal tracker, colour-code by days-to-expiry, assign owners, and chase the ones that slipped from last week.

    Effort
    ~6 hours/week, one account manager
    Systems involved
    Applied Epic, Google Sheets

  2. Personal-lines renewal re-marketing

    high automation potential

    For each renewal flagged with a rate increase over 10%, re-key the risk into the rater, compare indications across the panel, and prepare a remarket recommendation for the producer.

    Effort
    ~10 hours/week across two staff
    Systems involved
    Applied Epic, EZLynx Rating Engine, Google Sheets

  3. Website quote request triage

    high automation potential

    A quote request arrives in HubSpot and the shared inbox, gets manually qualified, re-typed into the rater, then re-typed a third time into Epic if it binds.

    Effort
    ~15 minutes per lead, ~40 leads/week
    Systems involved
    HubSpot, Google Workspace (Gmail), EZLynx Rating Engine, Applied Epic

  4. Certificate of insurance requests

    high automation potential

    Commercial clients email asking for an ACORD 25 naming a new certificate holder. Staff look up the policy in Epic, issue the certificate, and email it back. Almost all of these are routine and identical.

    Effort
    ~25 requests/week, ~10 minutes each
    Systems involved
    Google Workspace (Gmail), Applied Epic, CSR24 Client Portal

  5. Carrier commission statement reconciliation

    medium automation potential

    Twelve carriers send commission statements in twelve formats. Each is keyed into a spreadsheet and matched against expected commission from Epic. Variances are chased by email.

    Effort
    ~2 days/month, bookkeeper
    Systems involved
    QuickBooks Online, Google Sheets, IVANS Download

  6. IVANS download suspense clearing

    medium automation potential

    Carrier download records that do not auto-match to a policy fall into a suspense queue. Someone reviews the queue and matches them by hand — when they get to it.

    Effort
    ~3 hours/week
    Systems involved
    IVANS Download, Applied Epic

  7. Review solicitation and response

    high automation potential

    Nobody consistently asks satisfied clients for a review after a good claim outcome or a successful remarket, and negative reviews can sit unanswered for days.

    Effort
    Sporadic; no owner
    Systems involved
    Google Business Profile, Twilio, Applied Epic

  8. Storm-season proactive outreach

    medium automation potential

    When a named storm is forecast for the Carolinas, someone pulls a list of coastal and flood-exposed insureds and sends preparation reminders. It happens when someone thinks of it.

    Effort
    Ad hoc, 2–3 times per season
    Systems involved
    Applied Epic, Twilio, Google Workspace (Gmail), Facebook

This table is the whole inventory. There is no machine-readable copy of it — if you want this list, you read this page. Nothing in it is connected to anything, either: Greene is a fixture, and no live credential exists for any of these products.