Verando: a candidate-record prototype closed after the business case remained unvalidated.
Verando was built to test whether franchise development teams and counsel still had to reconstruct candidate application and disclosure activity across different systems. The deterministic prototype connected fixed intake, the selected Franchise Disclosure Document (FDD) version, recorded software activity, a review-period date, candidate receipt acknowledgment, and staff actions in one brand-specific record. It recorded product activity for human review. It did not provide legal advice, certify compliance, prove lawful delivery, or determine signing eligibility.
Archived synthetic demonstration. Verando is not an active product, customer deployment, or real-candidate service.
Franchise-team concept
The prototype explored whether one brand-specific record could answer the complete-record question without rebuilding the file across separate tools.
Candidate-side concept
The candidate walkthrough showed an FDD version, recorded activity, review-period date, and separate receipt acknowledgment for one brand-specific application.
Archived prototype
What it contained
This synthetic preview preserves an interface study, not an exact capture of every archived signed-in screen. Choose a perspective to keep staff controls and candidate screens separate.
Candidate queue
4 synthetic recordsThis interface study used safer terms than parts of the archived signed-in prototype. Open a synthetic record to inspect the intended format.
A short application checked against brand-set requirements.
The prototype form collected state, liquid capital, net worth, and credit score, compared them with brand-set thresholds, then stored the state and yes/no results rather than the raw financial values. It displayed an automated qualified or not qualified result and had no complete correction or recourse path. That issue was unresolved when Verando closed.
Record when an FDD version is made available.
When staff made a specific FDD version available in the prototype, it recorded the document version and server time. Candidate access was served from private storage through a short-lived signed link. This was a recorded software event, not independent proof of lawful delivery.
Track a review-period date from the recorded event.
The prototype calculated 14 calendar days from a staff-recorded software event and displayed day 7, day 12, and day 14 milestones. That event was not independent proof of delivery or receipt, and the date was not a signing authorization. The software did not determine which federal or state rules applied.
Prototype calculation: 14 days from the recorded event.
Day 9 of 14 · July 17, 2026 · Marcus Reyes (sample)
Day 7 milestone recordedDate calculated from the staff-recorded event: July 22, 2026. The event is not independent proof of delivery or receipt. The date is not authorization to sign or pay. Illustrative data.
Show brand-set requirement checks for staff review.
Verando compared submitted answers with configured thresholds and stored deterministic Boolean results. The signed-in prototype turned those results into a qualification label. Human authority was the intended boundary, but the label, explanation, correction, and review path were not ready for live use.
Record a separate typed-name receipt acknowledgment.
The candidate-side prototype recorded a typed name, consent, candidate account, server time, and event linkage. The exact acknowledgment text was not versioned or cleared by counsel, so this is not presented as a complete Item 23 artifact.
In the prototype, a typed name recorded receipt. It was not a signature on any agreement, and only the candidate account could submit it.
Bring the candidate record into one exportable view.
The prototype generated a PDF from stored application results, FDD events, candidate access time, acknowledgment, and logged annotations. The software did not determine legal meaning or identify everything that might be missing.
The archived signed-in PDF used legacy compliance, completion, and signing-eligibility language. The screen shown here was a replacement study, not a shipped export. Naming, provenance, and counsel review were unresolved when Verando closed.
Case study decision
What I built, what remained unproven, and why I stopped.
Existing franchise platforms already manage candidates, FDD delivery, signatures, waiting periods, and onboarding. Verando explored a narrower complete-record question, but competitive overlap was substantial and demand for that wedge was not validated. I closed the venture on August 7, 2026.
Public product references: ClientTether (opens in a new tab), FranConnect (opens in a new tab), FranchiseLauncher (opens in a new tab), and FranchiseSoft (opens in a new tab). These are vendor descriptions, not independent product tests.
Deterministic record prototype
The prototype connected fixed intake, versioned FDD storage, recorded software events, candidate access time, receipt acknowledgment, staff actions, access controls, and a PDF route.
Trust boundaries tested in code
Automated tests covered tenant isolation and selected access boundaries. Staff MFA and private document storage were implemented. These controls were not an external security or compliance certification.
Why I stopped
Established franchise platforms already cover much of the workflow. Verando had no verified customers, pilots, revenue, willingness-to-pay evidence, or validated ICP, so I closed the venture instead of presenting the remaining wedge as proven.
What remained a hypothesis
A complete-record layer and source-linked AI review might have collected evidence across systems and flagged gaps. Neither the commercial value nor the AI layer was validated, built for production, or opened for real-candidate use.
Tested safeguards
Security and boundaries in the archived prototype
The prototype recorded software state, not legal conclusions. The federal Franchise Rule generally requires the FDD at least 14 calendar days before signing or payment, but a Verando timestamp does not independently establish that the legal clock began. Read the FTC Franchise Rule (opens in a new tab).
Tenant isolation, tested
Row-level security tests covered brand, candidate, application, document, storage, and gated passport-table boundaries. These were code- and test-backed controls, not an external certification.
MFA-gated staff access
The implementation required MFA for staff access to sensitive operational records. Owner-scoped row-level security limited candidate accounts to their own records.
Private document storage
The tested implementation stored documents in private buckets and served them over short-lived signed links.
Minimal intake retention
For threshold checks, the prototype kept state and derived yes/no results rather than raw liquidity, net-worth, or credit-score values.
Did not replace franchise counsel.
The prototype organized records and surfaced workflow state. It did not determine whether a transaction complied with federal or state law.
Did not ship document AI.
Confidential-document AI was never an approved production feature. Source-linked review remained a future concept, not part of the archived prototype.
Was not ready for live qualification decisions.
Configured rules were deterministic, but the signed-in prototype still used a qualified or not qualified label and lacked a complete correction and recourse path.
Did not rely on UI filters for tenancy.
PostgreSQL row-level security enforced brand isolation at the database, backed by automated cross-tenant tests.
Completed case study · Closed August 2026
Verando is closed as an active venture.
What I built: fixed intake, deterministic requirement checks, versioned FDD storage, recorded software events, candidate access time, acknowledgment, access controls, and a PDF route.
What never reached live use: brand-specific grouping, neutral terminology, correction paths, versioned acknowledgment text, document provenance, counsel review, Candidate Passport portability, and source-linked AI review.
Why I stopped: incumbent overlap was substantial, and Verando had no verified customers, pilots, revenue, willingness-to-pay evidence, or validated ICP. The remaining complete-record wedge was a hypothesis, not a proven business.
This site is an archived case-study demonstration using synthetic data. It is not an active product or franchise service.