FuturaSight Screens
Screens that stay current, even offline.
Overview
FuturaSight Screens is a private SaaS product from Futura Sight for restaurants and other multi-location businesses. The public site introduces the product, its core workflow and a manually reviewed business signup. The internal dashboard is not publicly accessible.
The challenge
Multi-location teams need menus, promotions and brand content synchronized across screens without sending someone to every location. Content changes constantly, staff time is limited, and connectivity cannot be taken for granted.
What I built
The public experience leads with the operational promise rather than feature jargon: organize screens by location and time zone, schedule weekly playback with repeats and pauses, keep playing when the internet drops, and isolate each business’s media library. The signup path sets expectations clearly: every business is reviewed manually before activation.
Scope
- Public product landing page and value proposition
- Login and business signup entry points
- Responsive presentation of screens, scheduling and offline playback
- Clear, low-friction path to request access
Research notes
- The public landing page shows the product’s main surfaces: a content panel, screen and branch counts, scheduled playback and a live status.
- The four product claims visible are multi-location organization, real scheduling, offline-first playback and a private media library.
- The signup page asks for a business name, contact name, email, password and main branch time zone. It states that access is activated after review.
Public signal
- Astro asset paths (/_astro/Layout.*.css)
- Tailwind CSS utility output
- Cloudflare Insights analytics beacon
- Public routes: /, /login and /registro
- No public pricing, dashboard or API documentation
What I couldn’t verify
The internal dashboard, scheduling engine, storage layer, billing and backend are private and were not inspected. No performance, customer or revenue claims are made here.