Live · client system
Juliana is a black & grey realism artist in Jacksonville. She had no website — her Instagram was doing that job — and her paperwork lived on paper. We built the public site and the whole system behind it: a bilingual waiver clients sign on their phone, a signed PDF record for both sides, private proof-of-age capture, client records, portfolio publishing she controls herself, and a calendar that appears on her iPhone.
01 what her clients see
02 what she sees
03 what gets signed
Dashboard screens throughout this page are shown on Blackline Studio — an identical build of the same platform running on sample data. We don't open a client's real records to show you a case study.
None of this was a design problem. It was an operations problem wearing a website's clothes.
The brief that came out of that: make the paperwork disappear into the phone, and give her one place to look.
The same records, approached from two directions.
on their own phone
on her phone or a laptop
One screen, one job. Every caption ends with what it means for the business.
01
The gallery on the homepage is rendered from her own database on the server, not pasted into the page. When she posts a new piece from the dashboard, the public wall has it on the next load.
She never has to ask anyone to update her website again.
02
English and Portuguese, switchable at any point without losing what's already been filled in. Eighteen-plus is validated before anything else, and the whole flow is built for a phone held in one hand.
Nobody signs a legal document they can only half read.
03
Signing produces a real PDF: the studio's header, every question and the client's answer, the initialled consents, the signature, the timestamp. It goes to her inbox and to the client's, and it can be regenerated any time from the dashboard.
Both sides hold the same document. No one has to trust a screenshot.
04
Name, phone, or record number. Health notes are flagged before the session. Countersigning is one tap. Records can be archived, and permanent deletion is deliberately awkward to reach.
A records request stops being an afternoon of digging through a box.
05
Sessions are booked in the dashboard, and the calendar publishes a private feed her iPhone subscribes to once. From then on her studio schedule is simply in her calendar app, next to everything else.
She checks her day the same way she already checks her day.
06
Signing a waiver creates or matches a client automatically by phone and email. Each one carries notes, a work log, and every waiver they've ever signed.
The regular who came back after two years is one search away.
07
Pick a photo, add a title and placement, publish. Images are compressed in the browser before they're uploaded, so a full-size phone photo doesn't slow down her site for anyone.
The demo moment: post a photo, refresh the public site, it's there.
Where a system like this usually goes wrong, and what we did about it.
Every word of legal text lives in exactly one file. The form on the client's phone and the PDF they sign both read from it.
so the two physically cannot drift apartProof-of-age images and scanned paperwork are stored privately and served only through an authenticated route. They are deliberately absent from the PDF and from every email.
so a leaked link can't expose a driver's licenceRecords archive with one tap. Permanent deletion only exists inside the archive, behind two confirmations and a warning about Florida retention rules.
so spam is easy to clear and real records are notDocuments are regenerated on download rather than frozen at signing, so a copy pulled after the session shows the countersignature.
so the record is never a stale snapshotThe subscription address carries a signed token. Without it the feed simply isn't there.
so her schedule isn't guessableAfter deploying we fetch what the server is actually serving and compare its fingerprint against what we meant to ship, then walk the pages in a real browser.
so a cache serving last week's version gets caught by us, not by herend to end
hers, not ours
We didn't write her legal text and we don't present it as ours. Our job was to make sure what she signs off on is exactly what her clients see and sign.
This system launched recently and she is still onboarding onto it. We are not going to invent a conversion lift or a percentage to put in a box. What we can offer instead is everything you can check yourself:
No testimonial appears on this page because we haven't been given one. When she offers one, it'll go here in her words.
The whole system is one Cloudflare Worker with a SQL database and an object store attached. No servers to patch, no separate hosting bill, and it runs close to the client wherever they are.
The public gallery is server-rendered into the page by streaming the database rows through an HTML rewriter, so it is fast and indexable rather than a client-side fetch. Uploads are compressed on the client before they ever reach storage. Sessions are signed rather than stored, and repeated failed logins lock the address out for a while. The calendar feed is a signed URL emitting standard iCalendar with a proper timezone block, which is why Apple Calendar accepts it without complaint.
A case study that ends at "launched" is usually hiding something. This one is a working relationship, and there is a list:
Software that stops changing is software nobody is using. We'd rather show you the list than pretend it's finished.
Forms you retype. Records in a shoebox. A thing only you know how to do. That's the part worth building. Tell us what yours is.