Senja StudioLet's Talk

CASE STUDY

Building Senja Studio
From Business Idea to Working Operations System

A service-business idea became a working foundation: a clear offer, a defined customer, organized projects, and connected booking, CRM, and follow-up systems.

Business
Senja Studio
Role
Business Operations + Project Lead
Focus
Positioning, systems, website, CRM, automation, launch infrastructure
The finished website — the visible part of a connected business foundation.
The finished website — the visible part of a connected business foundation.

01 / THE STARTING POINT

The business didn’t need more ideas. It needed structure.

The missing piece was sequence: define the customer and offer, organize the work, then connect interest to a booked conversation.

The priorities: one source of truth, visible projects, connected systems, and testing before launch.

Assess broadly.
Prioritize narrowly.
Implement sequentially.

02 / VOC + POSITIONING

First, clarify who the business is actually for.

Right-Hand Business Operations Support

Mila is a capable founder whose business has outgrown her systems. She needs practical help identifying priorities and fixing one system at a time.

Project Goal
Define a clear offer for a specific founder.
My Role
Business Operations + Project Lead
What I Built / Changed
Defined the model client, positioning, and discovery messaging.
Result / Proof
A customer and promise to guide the website and discovery call.
The model client and positioning that guided the build.
The model client and positioning that guided the build.
Turning business capabilities into discovery-page messaging.
Turning business capabilities into discovery-page messaging.

03 / BRAND EVOLUTION

The brand needed to feel as capable as the work.

The core themes stayed. The visual system evolved toward a more open, editorial expression of capable, human support.

Earlier direction — establishing the core themes.
Earlier direction — establishing the core themes.
Current website direction — clarity, contrast, and room to breathe.
Current website direction — clarity, contrast, and room to breathe.

04 / WEBSITE STRATEGY + DECISIONS

The website was designed around the client journey, not a service list.

Each section helps a founder recognize her needs, understand the support, see proof, and move toward a discovery call.

  1. 01Is this for me?
  2. 02Does she understand what feels messy?
  3. 03What can she help with?
  4. 04Can she actually execute?
  5. 05What happens next?
A client-focused promise and a clear discovery-call pathway.
A client-focused promise and a clear discovery-call pathway.
Practical service language connects the work to a founder’s needs.
Practical service language connects the work to a founder’s needs.
Existing client proof supports confidence in the work.
Existing client proof supports confidence in the work.

05 / BUSINESS-TECH ARCHITECTURE

The website was only one piece of the operating system.

A clear next step at every handoff.

  1. 01Website
  2. 02Discovery Call
  3. 03CRM / Opportunity
  4. 04Follow-Up Workflow
  5. 05Client Process
  6. 06Payment

06 / BUSINESS SYSTEMS + PROJECT EXECUTION

Build the structure behind the business.

Project Goal
Move business operations out of memory.
My Role
Operations Designer + Implementer
What I Built / Changed
Built the dashboard, documented systems, and tracked website execution and QA.
Result / Proof
One source of truth and a clear build-to-launch plan.
Pamela at her Senja Studio strategy workspace
Planning the work. Then doing the work.

FOUNDATION → BUILD → CONNECT → TEST → LAUNCH

Assess broadly. Prioritize narrowly. Implement sequentially.

INSIDE THE PROJECT

Proof Highlights

The working assets behind the story. Select any image to view it full size.

01 / BUSINESS HOME

Notion — the central dashboard keeps business information and working links together.
Notion — the central dashboard keeps business information and working links together.

02 / PROJECT EXECUTION

Asana — website implementation and QA organized into visible work.
Asana — website implementation and QA organized into visible work.

03 / SALES PIPELINE

FG Funnels — opportunity stages make the next step visible.
FG Funnels — opportunity stages make the next step visible.

07 / LEAD + SALES INFRASTRUCTURE

A lead needs somewhere to go after clicking the CTA.

Project Goal
Connect prospect interest to a booked conversation.
My Role
Systems + Client Journey Implementation
What I Built / Changed
Configured booking, CRM stages, and opportunity tracking.
Result / Proof
A visible status and next step for each lead.
The booking setup connects interest to a scheduled conversation.
The booking setup connects interest to a scheduled conversation.

08 / AUTOMATION + WORKFLOW INFRASTRUCTURE

The follow-up process should not live in someone’s head.

Project Goal
Reduce manual discovery-call tracking.
My Role
Systems + Workflow Implementation
What I Built / Changed
Built booking-triggered opportunity updates.
Result / Proof
Successful execution captured in test records.
Workflow logic connects the booking event to opportunity updates.
Workflow logic connects the booking event to opportunity updates.

BUILT. CONNECTED. TESTED.

The execution logs are the proof.

Test logs record successful opportunity lookups and updates.

Actual workflow execution logs — successful actions recorded during testing.
Actual workflow execution logs — successful actions recorded during testing.

09 / PAYMENTS + LAUNCH INFRASTRUCTURE

The business also needed to be ready to transact.

Project Goal
Prepare the business to accept payments.
My Role
Systems Setup + Launch Readiness
What I Built / Changed
Connected Stripe and PayPal.
Result / Proof
Stripe is the default; PayPal is connected.
Payment setup — Stripe as the default provider, with PayPal connected.
Payment setup — Stripe as the default provider, with PayPal connected.

10 / FINAL RESULT

The real deliverable was not a website. It was a working business foundation.

Clear direction

A defined offer, customer, and website.

Organized execution

A project plan and source of truth.

Connected systems

Booking, CRM, follow-up, and payment setup.

Tested workflows

Execution logs document successful test actions.

The finished desktop experience.
The finished desktop experience.
Clear services, supported by real work.
Clear services, supported by real work.
The same discovery pathway on mobile.
The same discovery pathway on mobile.

11 / CAPABILITIES IN PRACTICE

What this project demonstrates

Business Operations

Organizing information and priorities into working systems.

Growth + Customer Journey

Connecting positioning through booking and follow-up.

Project Execution

Taking defined priorities through implementation and QA.

Systems Implementation

Building workflows and documentation that reduce reliance on memory.

12 / THE WORK BEHIND THE WEBSITE

The real deliverable
was momentum.

The right decisions, in the right order — implemented, connected, tested, and documented.

That is the work behind the finished website.

QUICK PROJECT WALKTHROUGH

A closer look at the work.

A short video overview will be added here.

Video coming soon
Pamela Socorro, founder of Senja Studio, wearing a red sweater

READY WHEN YOU ARE

Need help turning business chaos into something that actually works?

Book a Discovery Call