StudioFolio: Creative Studio Showcase with Live Project Estimator

Problem and target customer

Why this exists

Customer problem

Indie creative studios lose qualified leads because their portfolio, pricing, and availability live on separate pages and tools, so prospects drop off before submitting an inquiry.

Who pays

Indie creative studio owners (2-8 people) running motion, brand, or design work who need a single site that showcases work, estimates scope, and captures inquiries.

Business model

Monthly subscription with a paid workspace tier for studios that need multi-seat access, custom estimator rules, and inquiry exports.

Editorial note

StudioFolio is built for indie creative studios that want a portfolio site to do more than show work.

The live estimator turns a static services page into a scope and budget conversation before the inquiry is sent.

Team availability is surfaced on the same page so prospects can self-qualify timing before reaching out.

Choose your next step

What do you need next?

Evaluate the operating tradeoffs quickly, or inspect how to build the MVP.

Evaluate this ideaSee the cost and deployment preview

Compare the three operating paths at the default workload before opening the full calculator.

See cost preview Build this ideaInspect the build blueprint

Review MVP scope, workflow, states, data rules, architecture, and acceptance criteria.

Open blueprint

Evaluation preview

What would it take to run?

Directional infrastructure estimates for the current 500 bookings assumption. Open the full calculator when you are ready to change it.

Open full cost and deployment

ManagedSelected

$25-$85/ month

Managed app hosting, database, backups, and basic observability for the booking workflow.

Lowest operating effort

Lean self-hosted

$8-$48/ month

One small VPS running the app, database, media volume, and backup job.

Lowest baseline cost

More control

$45-$145/ month

Separate app, data, storage, and worker capacity for cleaner operations.

Most separation and control

Build blueprint

Build the first paid use case

Product goal

Who it serves and what it must change

Target user: Indie creative studio owners running motion, brand, or design work who need a portfolio site that also qualifies leads.
Problem: Studios lose leads because portfolio, pricing, and availability are split across pages and tools, so prospects drop off before submitting an inquiry.
Measurable outcome: At least 8% of estimator sessions on the live site result in a submitted inquiry with a usable scope brief within 30 days.

MVP scope

What ships now and what waits

Included

Portfolio showcase with case study pages
Live project estimator with scope and budget output
Team availability calendar tied to inquiry intake
Inquiry form with estimator output attached
Admin workspace for inquiries and availability

Excluded

Client delivery portal
Invoicing and e-signature
Public reviews moderation
Multi-language localization
Time tracking

UX and user flow

Screens, actions, and states

Portfolio home with case study grid

Portfolio home with case study grid

Review details

Case study detail page

Case study detail page

Review details

Live estimator panel

Live estimator panel

Review details

Inquiry form with attached estimator output

Inquiry form with attached estimator output

Review details

Admin workspace with inquiry inbox and availability editor

Admin workspace with inquiry inbox and availability editor

Review details

Primary flow

Visitor opens the portfolio home
Visitor opens a case study
Visitor opens the estimator and selects scope, deliverables, and timeline
Estimator returns a budget range and flags dates against team availability
Visitor submits an inquiry with the estimator output attached
Admin reviews the inquiry in the workspace and updates availability

Loading, empty, and error states

Estimator idle
Estimator calculating
Estimator returning budget range
Estimator blocked because no team slots match the requested dates
Inquiry submitted
Inquiry marked reviewed

Core entity outline

Entities and business rules

StudioProfile

StudioProfile

Fields: id, status
Relations: Supports the primary workflow

CaseStudy

CaseStudy

Fields: id, status
Relations: Supports the primary workflow

EstimatorRule

EstimatorRule

Fields: id, status
Relations: Supports the primary workflow

AvailabilitySlot

AvailabilitySlot

Fields: id, status
Relations: Supports the primary workflow

Inquiry

Inquiry

Fields: id, status
Relations: Supports the primary workflow

Business rules

Estimator output is recomputed whenever scope, deliverables, or timeline changes
An inquiry can only be submitted if the estimator produced a budget range
Availability slots block estimator dates that fall fully inside a booked range
Admin can mark an inquiry reviewed, which freezes the attached estimator output

Architecture and data flow

Components, integrations, and controls

Lovable front end for portfolio, estimator, and admin

Lovable front end for portfolio, estimator, and admin

Railway Postgres for studios, case studies, estimator rules, availability, and inquiries

Railway Postgres for studios, case studies, estimator rules, availability, and inquiries

Railway object storage for case study media and estimator exports

Railway object storage for case study media and estimator exports

Make scenario for inquiry routing and availability sync

Make scenario for inquiry routing and availability sync

LLM API for summarizing inquiry briefs in the admin inbox

LLM API for summarizing inquiry briefs in the admin inbox

Integrations

Calendar API for team availability slots
LLM API for inquiry brief summaries
Email or Slack via Make for inquiry notifications
Object storage for case study media

Data flow

Visitor submits estimator inputs to Lovable
Lovable calls the estimator engine on Railway and returns a budget range
Visitor submits the inquiry form with the estimator output attached
Railway persists the inquiry and triggers a Make scenario
Make routes the inquiry to email or Slack and logs the activity

Failure handling

Estimator falls back to a default budget range if a rule is missing
Calendar API failures show availability as unknown and warn the visitor
LLM summary failures still persist the raw inquiry brief
Inquiry form retries on transient database errors

Security

Admin auth for the workspace
Public read access only for portfolio and estimator
Rate limiting on the estimator endpoint
Signed URLs for case study media

Rate limits

Estimator calls limited per session to prevent abuse
Inquiry submissions limited per IP per hour
Admin login attempts throttled after repeated failures

Deliverables and acceptance

Definition of done for the MVP

Deliverables

Live portfolio site with case studies
Live estimator with budget range output
Team availability calendar on the inquiry page
Admin workspace with inquiry inbox and availability editor
Inquiry routing to email or Slack via Make

Acceptance criteria

Estimator returns a budget range for every valid scope input within 2 seconds
Inquiry form rejects submissions without an estimator output
Availability calendar blocks dates that fall inside a booked slot
Admin can mark an inquiry reviewed and the estimator output is preserved
Inquiry notifications reach email or Slack within 2 minutes of submission

Recommended stack

Enough technology for the first version

Implementation

Lovable for the public site, estimator UI, and admin workspace

Implementation

Railway for Postgres, object storage, and scheduled jobs

Implementation

Make for routing new inquiries to email or Slack and syncing availability changes

Implementation

Calendar API for team availability slots

Implementation

LLM API for summarizing inquiry briefs in the admin inbox

Why this is sufficient

Lovable covers the editorial portfolio, estimator, and admin screens; Railway hosts Postgres for inquiries, availability, and activity logs plus object storage for case study media; Make handles bounded glue between the inquiry form, email/Slack, and calendar sync; the LLM API is used only to summarize incoming inquiry briefs for the admin inbox.

Not required for the MVP

Custom CRMPayment processing for depositsMobile native appsReal-time collaborative editing

Next stepTurn the blueprint into an execution plan

Copy the build prompt, model the operating cost, and choose where to deploy.

Build and ship

Execution

Build, price, and deploy the MVP

Once the blueprint is clear, use the prompt, cost model, and deployment options to start building.

Build prompt

Copy this into a builder

lovable

Build prompt

Your build prompt is ready

Open the prompt pack whenever you are ready to take this blueprint into your builder.

Based on the blueprintReady for your builderFollow-up steps included

Cost calculator

Model the MVP operating cost

A technical run-cost estimate for the first production version. Team, acquisition, payment fees, and business COGS are excluded.

Estimated monthly total$25-$85

$13-$43 per 250 bookings

Bookings / month500 bookings

Selected pathEasiest

Pricing checkedAug 2, 2026

Cost breakdown

$25-$85 per month

Low and high values allow for usage variance and plan headroom.

Managed infrastructure

Managed app hosting, database, backups, and basic observability for the booking workflow.

50K bookings included, then $8-$20 per 100K bookings

$25-$65

Calendar API

Calendar API is implied by the source workflow or feature list.

Monthly allowance from this idea's operating profile

$0-$20

Included

Application hosting
Relational database
Basic backups
appointments, availability, and intake details state
Calendar API

Not included

Paid acquisition
Founder or team time
Tax or legal review
Custom enterprise procurement

Pricing basis

The estimate combines the selected infrastructure path, required operating modules, selected optional modules, and usage above included monthly allowances. Taxes and regional uplifts are excluded.

Managed app baseline Google Calendar API documentation

Deployment options

Pick the operational tradeoff

Choose based on operating preference, not only the headline price.

EasiestRecommended

Railway

Fast Docker deployment for the app, database, worker, and preview workflow without managing a VPS.

$15-90/month before usage-heavy add-ons

Good fit

Fast setup
Low starting cost
Good preview workflow

Limitation

Usage billing needs active monitoring as traffic and jobs grow.

Open Railway

Cheapest

Vultr

Run the app, worker, and database on one small Vultr VPS with Docker Compose and explicit backups.

$8-60/month before managed add-ons

Good fit

Predictable baseline
Portable setup
Room for workers

Limitation

You own patching, backups, monitoring, and incident response.

Deploy on Vultr View the lean VPS guide

More control

DigitalOcean

Separate application, worker, data, storage, and backup responsibilities as the workload grows.

$10-120/month before managed add-ons

Good fit

Cloud VPS control
Global regions
Room for workers

Limitation

You own server setup, patching, backups, and operational monitoring.

Explore DigitalOcean View the separated cloud guide

Start building

Prototype, automate, then deploy

Recommended route

01Vibe-coding builderBuild StudioFolio in Lovable

Use Lovable to assemble the editorial portfolio, live estimator UI, team availability calendar, inquiry form, and admin workspace with auth.

Open Lovable 02AutomationWire inquiry and availability glue in Make

Use Make as bounded glue to route new inquiries to email or Slack and to sync team availability changes back to the calendar source.

Open Make 03DeployHost data and media on Railway

Use Railway to run Postgres for inquiries, availability, and activity logs, plus object storage for case study media and estimator exports.

Open Railway

StudioFolio: Creative Studio Showcase with Live Project Estimator

Is this worth validating?

Build this if

Avoid this if

Validate first

Why this exists

Customer problem

Who pays

Business model

What do you need next?

What would it take to run?

Build the first paid use case

Who it serves and what it must change

What ships now and what waits

Included

Excluded

Screens, actions, and states

Primary flow

Loading, empty, and error states

Entities and business rules

Business rules

Components, integrations, and controls

Integrations

Data flow

Failure handling

Security

Rate limits

Definition of done for the MVP

Deliverables

Acceptance criteria

Enough technology for the first version

Lovable for the public site, estimator UI, and admin workspace

Railway for Postgres, object storage, and scheduled jobs

Make for routing new inquiries to email or Slack and syncing availability changes

Calendar API for team availability slots

LLM API for summarizing inquiry briefs in the admin inbox

Why this is sufficient

Not required for the MVP

Build, price, and deploy the MVP

Copy this into a builder

Your build prompt is ready

Model the MVP operating cost

Usage assumptions

$25-$85 per month

Included

Not included

Pricing basis

Pick the operational tradeoff

Railway

Good fit

Limitation

Vultr

Good fit

Limitation

DigitalOcean

Good fit

Limitation

Prototype, automate, then deploy

Related ideas

BoxStory: Storytelling DTC Product Landing Page Builder

AgencyOS: Agency Website & Lead Engine

Interior Designer Portfolio with 3D Mood Board Builder

ShutterFolio: Creative Photographer Portfolio & Inquiry Engine

BuildBid: Residential Contractor Lead Capture & Estimator

Wedding Venue Showcase & Inquiry Management Platform