Skip to content

Case study · Website + admin system

A creative studio, rebuilt as a system.

A creative studio’s public site and private admin, built as one system the studio runs itself.

Visit createdmotionstudios.com (opens in a new tab)Live
The Created Motion Studios home page at desktop width, with its navigation, headline, and the studio’s three service figures.
The Created Motion Studios home page on a phone.

01 — The brief

Where the business stood.

Created Motion Studios is a principal-led creative studio in Jacksonville, making films, photography and campaign content across six service lines: photography, real estate, video, drone, events, and business content.

A studio selling six kinds of work has to make each one easy to find and easy to ask about, and every inquiry has to reach the studio in a form it can act on — without a developer standing between the owner and the studio’s own website.

02 — What we built

The system, end to end.

Treat the website and the business behind it as one system: a public site that presents the six services, and a private admin where inquiries, projects and the portfolio are run, both reading from the same source of truth.

An inquiry

  1. Service page

    Six services, each with a page and packages of its own.

  2. Inquiry form

    Opened from a package, it starts with the service chosen.

  3. Saved record

    Every inquiry is kept as a record, not left in an inbox.

  4. Private admin

    It arrives as New, and the studio gets an email alert.

The portfolio

  1. Private admin

    The studio adds its work, by service.

  2. Visibility

    Each piece is switched visible or hidden.

  3. Work archive

    Only what is visible appears, filtered by service.

The studio admin’s dashboard, shown with demonstration data: counts of active projects, new inquiries, deliverables and events, above the active projects, recent inquiries and the week’s schedule.
The admin’s inquiry list, shown with demonstration data: inquiries by stage from New to Won, with one open beside the list.
One private admin for the studio owner: Dashboard, Projects, Inquiries, Portfolio, Calendar and Settings. Admin screens on this page show demonstration data, never a real inquiry.

03 — Key decisions

Where the thinking shows.

The Created Motion Studios photography page: the service introduced, its starting rate, and a Start a Project button.
The Created Motion Studios photography page on a phone.

Every service is a way in.

Each of the six services has its own page, and every package on it opens the inquiry form with the service already chosen and the package already named. A visitor never has to translate what they want into the studio’s categories.

One inquiry in the admin, shown with demonstration data: a fictional client’s brief and details, marked New, with Reply and Convert to Project.
The Created Motion Studios inquiry form at its first step, asking what is being made.

An inquiry is a record, not an email.

Every inquiry lands in the admin as New, with a reference of its own, and the studio is alerted by email. The record comes first, so a missed email never means a missed inquiry.

The admin’s portfolio manager, shown with demonstration data: each piece marked visible on the website or hidden, by service.
The Created Motion Studios work archive, with filters for photography, video, drone, events and business content.

The studio decides what is public.

Every piece in the portfolio is switched visible or hidden, and the public archive shows only what is visible. Publishing new work needs no developer and no deploy.

04 — Gallery

The site, on every screen.

The Created Motion Studios pricing page, with starting rates for each service.
  • The Created Motion Studios about page on a phone.
  • The Created Motion Studios pricing page on a phone, with each service’s starting rate.
  • The Created Motion Studios work archive on a phone.

05 — Under the hood

What it runs on.

  • Next.js
  • TypeScript
  • Supabase
  • Resend
  • Vercel
01

One connected system

The public site and the private admin as one deployment, reading the same records.

02

An admin the studio runs

Projects, inquiries, the portfolio and the calendar in one place, built for the owner.

03

Inquiry management

Every inquiry becomes a record with a status and a reference, from New onward.

04

Portfolio control

What the public archive shows is the studio’s switch. No developer, no deploy.

Built on Next.js, Supabase and Resend, on Vercel, with separate preview and production databases, so each stage was reviewed without touching live inquiries. Inquiries are rate-limited and deduplicated; a visitor’s IP is kept only as a keyed hash, for 30 days.

06 — Outcome

What exists now.

The studio runs its own site: inquiries arrive in the admin ready to act on, the portfolio is published from the same place, and the public site presents six service lines with a clear way to ask about each.

Visit createdmotionstudios.com (opens in a new tab)All work

Start a project

Tell us what you need built or improved.

A short message is enough to start. We’ll come back with a clear read on scope and the right next step.

Start a Projectchristian@hayeslabs.io