A restaurant-group disclosure operations layer that maps reviewed fee rules to each publishing surface and preserves source-linked evidence of what guests saw.
Genesis score7.25/10
Make Feefront real.0/500
500 more votes and Feefront is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
Jul 1, 2026Florida effective date
0Dedicated direct peers found
0Verified core integrations
The case
Restaurant groups can configure service charges, automatic gratuities, card surcharges, delivery fees, and other mandatory charges differently across locations and channels. Feefront turns counsel-approved rules into publishable requirements, detects mismatches, and records exact versions and evidence. It never decides legal applicability from a fee label, guarantees compliance, or treats a signed publication record as proof that every guest saw or understood a disclosure.
Who pays — and why
Legal, finance, digital, operations, and franchise leaders at multi-location restaurant and hospitality groups.
What it unlocks
A per-location fee register with amount or formula, mandatory status, purpose, recipient, tax treatment, channel, effective dates, and reviewed authority
Publication requirements mapped separately to physical menu, website, application, ordering, checkout, and receipt surfaces
Version comparison and evidence capture that expose missing, stale, conflicting, or unsupported disclosures
Signed release receipts that establish artifact integrity and approval history without claiming legal compliance
How Genesis scored it
7.25across seven criteria
9
Temporal window
The confirmed requirement is already effective.
8
Buyer persona
Multi-location restaurant legal and operations teams are specific.
5
Convergence
One cross-reference and one inbound link provide limited echo.
Why it scored well
A confirmed live Florida requirement, broad restaurant scope, a precise multi-location buyer, and no dedicated peer found support the concept.
What's holding it back
No core interfaces are verified, legal interpretation and managed onboarding add cost, and point-of-sale providers can absorb the workflow.
Signals detected4 sources crossed
Signalofficial and legal research carried in Genesis
Signalauthority research carried in Genesis
SignalGenesis market scan
SignalGenesis evidence audit
Direction brieffeefront.md
feefront.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.
