φιλία
Sign inGet a room

chair .

Your clients chat. ADAM handles the small asks. You plate every change before it leaves the kitchen. Hours land on the check in real time — no surprises at month end.

Open kitchen in the back. Calm dining room out front. Two rooms, one evening.

Free during early access. No card, no welcome series, no “onboarding journey.”

Cedar Homes · today
on the stove
A
Ava8:14 AM

Can we make the pricing card a little lighter? Feels too loud next to the testimonial.

ADAMthe ai8:14 AM

On it. I'll try a few weights and a softer background. Pulling up the pricing card and branching from main.

9:02 — diff on the pass
components/pricing-card.tsx+2 −2
<Card className={
− "bg-primary text-primary-foreground"
+ "bg-card border border-border/60"
}>
− <h3 className="font-bold text-2xl">
+ <h3 className="font-serif text-xl">
φιλίαphil·í·a /fee-LEE-ah/

Greek noun. Friendship between equals. The bond a great restaurant builds with its regulars — not a contract.

The problem

You didn’t start a studio so you could spend your week chasing replies.

But here you are. Slack threads at midnight. Half-typed proposals. Status updates you keep meaning to write. Three browser tabs of invoicing, four of design files, one of a contract from 2024 you still owe a signature on.

The work, the actual making, is the thing you love. The host work is what’s eating you.

“A studio is not an inbox. It’s a kitchen — and every kitchen needs a host.”

— Phillia, the manifesto

Why we’re different

Run your agency without being the bottleneck. Stay in the loop on every action.

VAs are slow. Snapshot vendors don’t know your clients. White-label portals feel one-size-fits-all. Phillia is the calm client-facing layer where ADAM handles small asks and you fire every change from the pass.

  1. Other tools

    A VA on a Slack channel, slow on a Tuesday morning.

    Phillia

    ADAM, here when you need it. You fire from the pass.

    Every client ask hits your pass for a yes-or-no before anything happens. You stay in the loop on every action — no surprises, no rogue automations.

  2. Other tools

    Time tracking on a spreadsheet, billed at month end.

    Phillia

    Hours land on the running tab in real time.

    Each course swap logs realistic billable hours and the client sees the check live. End-of-month invoicing is the same number they've been watching all month.

  3. Other tools

    A white-label client portal, one-size-fits-all.

    Phillia

    A calm dining room for each client, scoped just for them.

    Each client connects only what they want at their own table. They see today's plate, the running tab, five course-swaps a month — never the back of the house.

The trio

Three people at every table — and one of them never sleeps.

  1. 01They order
  2. 02ADAM cooks
  3. 03You plate

One thread per project — like a four-top where the host, the chef, and the diners can all be heard. No inbox chaos, no #channel sprawl. Quiet hours respected, in your client's timezone.

quiet hours active in São Paulo

cedar homes · client table
Hey — can you tag the 50 webinar signups from yesterday as warm-leads? Then put them through the welcome sequence.
Ava · 7:05am
On it — I'll pass that to Sam (your host). They'll fire it shortly.
Iris · 7:05am
one thread per client quiet hours respected
on the stove
kitchen action · 0.5 hr
Tag 50 contacts in GHL as warm-leads + start workflow.
  • Reads notebook for "warm-leads" tag spelling
  • Cites it. Drafts the action.
  • Stages on the pass for Sam to fire.
ADAM never ships without your yes→ pass
the pass · sam, host7:06am
Cedar Homespending

Tag 50 contacts as warm-leads + start welcome workflow.

est. 0.5 hr · $37.50
client sees: "plated."you stay in the loop on every action

Dining room · client view

What your client actually sees.

Calm, curated, finished. The client never sees the prep clock, the diff, the back-and-forth. They see today’s courses, what’s plated, what’s still cooking, the running tab, and how many course-swaps they have left this cycle.

  • Status, not stack traces. On the stove. Plated. Served. No ticket IDs.
  • The tab is live. Every billable hour ADAM logs becomes a line item the client can read in real time.
  • Course swaps, not Slack threads. Five tweaks per cycle, each one a structured ask Iris reads back before firing.
philllia.com/cedar-homes
🏡

Cedar Homes

On the stove

Tuesday, May 10 · 4 course swaps left this cycle

Today’s courses

PlatedHomepage hero with warm dusk crop1.5h
CookingPricing page rewrite — three anglesby 3pm
OrderedListings carousel polish (course swap)fires after lunch
The running tab
$487.50
6.5 hrs at $75 · resets May 31
Course swaps left
4 / 5
One used: pricing-page rewrite
Iris is here. Ask anything.

Meet the cast

Three on the staff — all of them yours.

ADAM doesn’t work alone. Phillia ships with a small ensemble of AI roles, each with one clear job. New roles join the menu as the kitchen grows.

ADAMHead chef

The one who actually cooks.

Reads the project notebook, takes the order, drafts every change inside your tools, and stages it on the pass for your yes — overnight, if you let him.

IrisFront of house

The face your clients see.

Carries drafts and previews from kitchen to client. Reads the order back. Confirms course swaps. Named for Iris, the Greek messenger goddess.

ThemisBooks · cashier

The one who keeps the check honest.

Turns ADAM's prep clock into invoice line items. Holds the scales of order. Named for Themis, the Greek goddess of justice.

Coming to the menu: Sommelier (tone & voice), Maître d’ (onboarding & pacing), Sous chef (parallel kitchens), Pâtissier (final polish). Each new AI gets a clear job before we ship a line of code.

One evening at Phillia

One Tuesday, told in six time-stamps.

One ticket, one ask. The shape of every shift is the same: an order comes in, ADAM fires it, you plate it, the client sees a finished course.

  1. 8:14 AM
    Ava asks for a lighter pricing card
  2. 8:14 AM
    ADAM acknowledges, branches from main
  3. 9:02 AM
    ADAM ships diff to the QA queue
  4. 11:30 AM
    you approve · the client sees “plated”
  5. 2:08 PM
    ADAM drafts the standup, leaves it in your tray
  6. 5:00 PM
    Phillia writes tomorrow’s prep list, dims the lights

Built for

Hosts like Maya, who’d rather not be the bottleneck.

Maya runs a GoHighLevel agency with a dozen client subaccounts. Four retainer clients on her plate this week, a school run at 8am, dinner that shouldn’t be cold. Here’s a Tuesday morning on Phillia.

GHL agencies were the first we built for — the integrations are sharpest there. The same shape fits any service business that hosts clients: design studios, dev shops, marketing teams, consultants, anyone whose week looks a lot like Maya’s.

  1. Tue · 7am
    Maya opens Phillia with coffee, scans the pass
  2. Tue · 7:05am
    Cedar Homes asks ADAM to tag 50 webinar attendees as warm-leads
  3. Tue · 7:06am
    Maya reads the request, fires it from the pass
  4. Tue · 7:06am
    ADAM handles it. Iris confirms: plated.
  5. Tue · 7:06am
    Themis rolls 0.5 hrs into the running tab — Cedar Homes sees it live
  6. Tue · 7:10am
    Maya closes the laptop. School run.
“I run the floor. ADAM handles the rest.”— Maya, host

Maya is composite — every detail is real for someone, no detail is real for any one host. We don’t use clients’ names.

Early access

We’re hosting a small first table.

If you’re an agency owner who’s tired of being the only host in the room, leave us your email. We’ll send you an invite when there’s a chair free. Usually within a week.

Free during early accessBring your own clientsLeave whenever, take your data