inLayers product
inLayers.desktop
inLayers — our own client workspace
The private workspace every inLayers client gets: project updates, documents, meetings, messages and add-ons in one place, installable on a phone. We built it because email threads are where projects go to get lost.
the problem
Every client project produces the same scattered trail: a discovery form somewhere, files in three email threads, a meeting link that has to be found again, questions asked in whichever channel was open at the time. The client never quite knows where the project stands. The studio spends real hours answering "can you resend that?".
We wanted one door. A place a client opens — on a laptop or a phone — and sees everything that is theirs, and nothing that isn't.
the system
One private space per client, behind a magic-link login. No password to forget.
Overview — where the project stands, what happened recently, what's next. Documents — proposals, scopes, deliverables, each with its source and date, viewable in the browser. Meetings — scheduled sessions with a join-in-the-browser room and an add-to-calendar link. Messages — a single thread with the studio, read receipts, nothing lost in email. Useful links — the staging URL, the shared drive, the tool logins, in one list. Service add-ons — the small extras a client can switch on for their project. Discovery archive — the original discovery answers, always accessible, so decisions stay grounded.
On the studio side, an admin that creates a client, generates their onboarding and discovery links, and switches sections on or off per client — a design-only client doesn't need meetings; a retainer client needs everything. Onboarding submissions arrive as a PDF by email and land in Notion automatically.
It installs on the phone as an app, with its own icon, and works offline for what it has already loaded.
the layers
- Interface — Next.js 14 App Router · Tailwind · installable PWA with service worker · sidebar shell that collapses cleanly on mobile
- Database — Supabase Postgres with row-level security per client · Supabase Auth (magic links) · private storage buckets for client documents
- Automations — Resend for invitations and notifications · onboarding and discovery forms → PDF → email → Notion
- Documents — PDF generation with @react-pdf/renderer · in-browser document viewer
- Deployment — Vercel · same codebase as inlayers.studio, separate authenticated surface
the result
Clients get a single place that is theirs. The studio stops resending. Every project starts from the same structured onboarding and ends with the deliverables in the same place they were discussed. It's also the platform we build client portals on for other businesses — when a Quick Build says "client portal", this is what's underneath.
status
inLayers product. Live and in use with inLayers clients. Roadmap: an assistant trained on the project's own context, automated status updates, and deliverable review with inline comments.
ready to build?
start with a discovery session.
We map your situation, scope what’s possible, and give you a written proposal with a price before any work begins. If it turns out to be a quick build, we’ll tell you that instead.
Or just write: hello@inlayers.studio