← Work / Active files

[ CASE FILE / LA-STUDIO-FINDER ]

Shipped

LA Recording Studio Finder

A production directory that turns a fragmented studio search into a location-aware, comparable decision.

Role
Product designer, developer, researcher, and operator
Discipline
Full-stack product / directory operations
Year
2026
Strongest proof
Live / Production
Mighty MouseTests ways to make small AI models faster29.5% faster / 30 trials
LifeOpsTelegram agent that organizes plans and knowledgeUsed every day
Studio FinderSearch and compare LA recording studiosLive directory

Finding a studio is a local-data problem disguised as a search box.

Artists often compare studios across scattered social profiles, map listings, outdated websites, and word of mouth. Important differences—location, room type, equipment, services, and fit—are difficult to evaluate consistently.

The directory creates one browsable decision surface while giving individual studios durable, search-friendly pages.

A solo product spanning interface, data, and production operations.

I designed and implemented the product, built its studio data and update workflow, created the map and discovery experience, established content and SEO standards, and operate the Vercel deployment.

Directory listings summarize public business information. A listing is not an endorsement, and accuracy depends on an ongoing maintenance loop.

Declared ownership

Original directory product, data workflow, search experience, content system, deployment, and production operations. Studio facts originate from public business information and are maintained as directory data.

How the work moves.

  1. Input

    Studio sources

    Public business sites, location data, services, rooms, and amenities.

  2. State

    Directory records

    Normalized studio fields and editorial context form a maintained dataset.

  3. Decision

    Quality checks

    Required fields, content depth, route integrity, and duplicate review.

  4. Output

    Discovery UI

    Search, filters, map context, recommendations, and detail pages.

  5. Output

    Search surface

    Canonical metadata, sitemaps, index controls, and content audits.

  6. Failure path

    Correction loop

    Stale facts, closed studios, and thin records return to review.

Decisions that changed the system.

Selected implementation record.

01 / MODEL

Comparable studio records

Unstructured public information becomes consistent fields and editorial summaries.

02 / DISCOVER

Map and directory experience

Visitors move between geographic context, filters, recommendations, and studio detail.

03 / PUBLISH

Search-ready route system

Canonical pages, sitemap policy, metadata, and parameter controls support discoverability.

04 / OPERATE

Production audit loop

Scripts and review procedures detect thin, JS-dependent, stale, and incorrectly indexed pages.

Claims with their edges left on.

HS-7VERIFIED RECORD
Live

Production

The directory is deployed on Vercel with a custom production domain.

SourceDEPLOYMENT.md and production deployment configuration

HS-7VERIFIED RECORD
Map + filters

Discovery model

Visitors can compare studios through geographic and structured directory context.

HS-7VERIFIED RECORD
Indexable

Search foundation

Canonical routes, sitemap controls, thin-page audits, and content standards support organic discovery.

SourceProduction audit and sitemap documentation

What failed stays in the record.

resolved

More pages did not automatically create more value

Observed
Thin or repetitive directory pages risked weak visitor utility and weak search performance.
Response
Introduced content-depth checks, public-route probes, and an audit that flags thin indexable pages.
resolved

Filter URLs can pollute the search index

Observed
Tracking and query variants can create duplicate or low-value route combinations.
Response
Canonicalize filter surfaces, redirect tracking parameters, and keep the sitemap restricted to intended public pages.
monitoring

Directory facts age

Observed
Rates, rooms, equipment, and business status change independently of the application.
Response
Maintain a correction and update workflow; avoid presenting public-source data as permanently verified.

Shipped and operating in production.

The public directory, map-based discovery experience, studio pages, SEO controls, and production audit workflow are live. The active work is improving content quality, directory coverage, and the path from discovery to a confident studio choice.

Open to the right work

A useful system starts with the actual problem.

Full-time product, automation, and technical-operations roles are the priority. Select workflow and creative-technology projects are open.