Multi-site outpatient care network
This fictional fixture represents a regional healthcare operator coordinating patient access, referral intake, and revenue-cycle work across a growing clinic footprint.
Portfolio project / Evidence-first sales research
AccountBriefAutomated account-research assistant.
Turn a real company name or domain into a sourced, reviewable account brief—without turning missing data into confident fiction.
01 / Interactive system
Research with a visible evidence boundary.
Public-source research, clearly labeled
Real-company searches use fixed Wikimedia endpoints through this site. Results show sources, retrieval time, confidence, and missing fields. No personal contacts are generated, no entered URL is crawled, and no buying signal is invented.
Loaded the offline synthetic Northstar Health Systems fixture.
Offline synthetic fixture
Fixture evidenceNorthstar Health Systems
northstar-health.example
Healthcare operations
The fixture consistently describes outpatient services, patient-access workflows, and revenue-cycle operations.
500–1,000 employees
A fictional careers snapshot and clinic directory support a range rather than an exact headcount.
Possible pain points
Referral intake may require duplicate entry
The fixture’s operations note describes fax, portal, and phone referrals converging into one central team, suggesting avoidable re-keying and status follow-up.
Eligibility checks may constrain scheduling
A synthetic job description emphasizes manual benefit verification before appointments and escalation of incomplete records.
Decision-maker role hypotheses
VP, Patient Access
Likely workflow owner for referral intake, scheduling quality, and access-center performance.
Chief Information Officer
Likely technical stakeholder for integration, security review, identity, and clinical-system constraints.
Buying signals, with evidence attached
Patient-access automation role opened
The synthetic careers snapshot includes a newly listed director role responsible for workflow standardization and automation pilots.
Two clinics added to the network
The fictional organization update describes expansion that could increase intake volume and process variance.
05 / Human discovery
Questions before conclusions
These are questions—not assertions. They turn hypotheses into a measurable discovery conversation.
- 01
How many referrals arrive through each channel, and where is the same information entered more than once?
- 02
Which eligibility exceptions consume the most staff time before an appointment can be confirmed?
- 03
What accuracy, privacy, and human-review thresholds would an automation pilot have to meet?
- 04
How would recovered capacity be measured without assuming it becomes immediate payroll savings?
06 / Personalized outreach
A draft with a human gate.
Every sourced fact points back here.
Synthetic service-line profile
Fictional description of services and operating model.
Synthetic clinic-network update
Fictional footprint and expansion update.
Synthetic careers snapshot
Fictional roles and responsibilities; not a live job board.
Synthetic operations interview
Fictional workflow notes created for evaluation.
Loaded source IDs: NS-01 · NS-02 · NS-03 · NS-04. Fixture content is fictional and exists only to demonstrate product behavior.
02 / Accessible architecture
A pipeline built to stop unsupported claims.
Read left to right on larger screens or top to bottom on mobile. The ordered list remains understandable without its visual connectors.
- 01
Input boundary
Accept a company name or public domain; normalize it, reject personal emails and private hosts, and cap request size.
- 02
Entity resolution
Search fixed Wikimedia endpoints, score organization evidence, and reject people, media, places, and ambiguous matches.
- 03
Evidence registry
Read structured public claims, preserve source URLs and retrieval time, and leave missing fields unknown.
- 04
Bounded synthesis
Separate sourced company facts from low-confidence workflow and role hypotheses. No people or contact details are created.
- 05
Claim guard
Expose field-level confidence, warnings, point-in-time qualifiers, limitations, and an honest not-found path.
- 06
Human review
A person verifies the company, evidence, recipient, tone, and proposed next step before any outreach.
03 / Product walkthrough
See the research boundary in motion.
The recorded walkthrough demonstrates the offline fixture path, claim-level evidence, outreach review, and safe abstention. The live interface above now adds sourced public-company resolution.
MP4 demonstrationWritten summary below
Read the written video summary
The recording opens an offline synthetic account fixture, reviews its summary and source IDs, checks pain-point and decision-role hypotheses, reads buying-signal warnings, copies a draft for human review, then searches an unmatched company to show that unsupported claims are withheld. Live public-company lookup was added after this recording and is available in the interactive section above.
04 / Fixture evaluation
Measure the behavior that earns trust.
Each fixture resolves through its exact company name and canonical domain.
Every offline-fixture claim carries confidence, at least one source ID, and a verification warning.
No fixture or fallback contains an invented person, email address, or phone number.
Each fallback withholds industry, size, pain points, roles, signals, and personalized outreach.
What this proves
The fixture suite verifies deterministic behavior, while mocked route checks cover entity disambiguation, structured claims, dated employee evidence, not-found handling, and provider failure. It does not prove that public records are complete or current, nor does it prove sales conversion or production readiness.
05 / Technology
Small architecture.
Strong boundaries.
- Next.js App Router
- React + TypeScript
- CSS Modules
- Deterministic fixture resolver
- Wikidata Action API
- Wikipedia Action API
- Organization entity scoring
- Source-indexed claim schema
- Browser Clipboard API
- Node test runner
- Cloudflare-compatible server route
06 / Safeguards
What the system
refuses to do.
No fabricated contacts
The prototype never invents names, email addresses, phone numbers, or reporting relationships.
Fixed public providers
Live lookup calls only Wikidata and Wikipedia endpoints. User-entered URLs are never fetched, preventing SSRF-style requests.
Unknown means unknown
An ambiguous or unmatched organization receives no invented facts, buying signals, people, or personalized outreach.
Claims stay inspectable
Public-source facts include confidence, source IDs, retrieval time, and a warning about what still needs verification.
Hypotheses look like hypotheses
Possible workflows and role archetypes are visibly separated from sourced company facts.
Human approval is final
Nothing is sent, saved to an account, or acted on automatically.
Project handoff