Skip to main content

Seb, 35 — Freelance Contractor

Who he is​

Seb is a freelance full-stack developer running his own company. He juggles 3-4 clients simultaneously, each with their own tools — one uses JIRA and Slack, another uses Linear and Discord, a third uses GitHub Issues and email. He context-switches dozens of times a day. His own company has admin too: invoicing, contracts, tax deadlines, time tracking. He's technically excellent but the overhead of managing multiple client worlds is eating into his billable hours.

His day before Morphee​

  • Morning: Opens laptop. Slack notifications from Client A. JIRA tickets updated overnight for Client B. An email from Client C about a scope change. Spends 20 minutes just figuring out which fire to put out first.
  • Context switch: Finishes a feature for Client A, needs to switch to Client B. Spends 15 minutes finding the right JIRA board, re-reading the ticket, remembering what he decided in last week's call. Where was that Slack thread about the API design?
  • Admin: Realizes he hasn't sent Client C's invoice for January. Opens his invoicing tool. What was the rate again? How many hours? Checks his time tracker — incomplete entries from last week.
  • Evening: Needs to prepare for tomorrow's call with Client A. What did they ask for in the last meeting? It's in his notes somewhere... or was it in Slack?

His day with Morphee​

Seb's Space hierarchy:

🏢 Seb Dev (company Space)
├── 💼 Client A — TechCorp
│   ├── 🚀 TechCorp API Refactor
│   └── 🚀 TechCorp Mobile App
├── 💼 Client B — StartupXYZ
│   └── 🚀 StartupXYZ MVP
├── 💼 Client C — AgencyPro
│   ├── 🚀 AgencyPro Dashboard
│   └── 🚀 AgencyPro Analytics
├── 📋 Admin (invoicing, contracts, taxes)
└── 🧠 My Space (personal notes, learning)

Each client Space has its own Interfaces — TechCorp's JIRA, StartupXYZ's Linear, AgencyPro's GitHub — all connected independently. Morphee knows which tools belong to which client.

[Morning, 8:30]
Seb: "Morning brief"
Morphee: "Good morning! Across your clients:

  🔴 TechCorp — API Refactor:
    - PR #89 has 2 merge conflicts (Sara pushed last night)
    - Sprint review tomorrow at 10am, you have 2 tickets in review
    - Slack: CTO asked about the caching strategy

  🟡 StartupXYZ — MVP:
    - Linear: 3 tickets moved to Ready, they're waiting on your auth module
    - No meetings today

  🟢 AgencyPro — Dashboard:
    - Quiet. Last commit was yours on Friday. Invoice due Feb 15.

  📋 Admin:
    - Client C January invoice: not sent yet (€4,200 — 28h × €150)
    - Tax quarterly deadline: March 15

  Suggested priority:
  1. Fix TechCorp merge conflicts (30 min)
  2. Reply to TechCorp CTO on caching (I've drafted a response)
  3. Send AgencyPro invoice
  4. StartupXYZ auth module this afternoon"

[Switching to TechCorp context]
Seb: "Open TechCorp API Refactor"
Morphee: "Switched to TechCorp API Refactor Space.
  I can see your JIRA board and Slack channels.

  Current sprint:
  - TECH-234: Payment endpoint refactor (In Progress — yours)
  - TECH-235: Rate limiting middleware (In Review — Sara reviewing)
  - TECH-238: Database migration scripts (To Do — assigned to you)

  Your last session (Friday):
  - You were refactoring the payment validation logic
  - Branch: feat/payment-v2, last commit: 'WIP: extract validator'
  - You noted: 'need to handle partial refunds edge case'"

[Quick context from a past meeting]
Seb: "What did their CTO say about caching last week?"
Morphee: "In the Feb 4 call, Marc (CTO) said:
  - They want Redis caching at the API gateway level
  - Budget for a managed Redis instance is approved
  - He prefers a 5-minute TTL for user data, 1-hour for product catalog
  - Concern: cache invalidation on inventory updates

  You agreed to prototype this week. Haven't started yet."

[Switching to admin]
Seb: "Generate Client C's January invoice"
Morphee: "AgencyPro — January 2026:

  📄 Invoice #2026-01-C
  Client: AgencyPro SAS
  Period: January 1–31, 2026
  Rate: €150/hour

  | Project | Hours | Amount |
  |---------|-------|--------|
  | Dashboard | 18h | €2,700 |
  | Analytics | 10h | €1,500 |
  | **Total** | **28h** | **€4,200** |

  Payment terms: 30 days
  Due date: March 2, 2026

  Want me to generate the PDF and send it to their accounting email?"
Seb: "Yes"
Morphee: "Invoice sent to compta@agencypro.fr ✓
  Saved in Admin Space. I'll remind you if not paid by March 2."

[End of day]
Seb: "Log my time today"
Morphee: "Based on your activity:
  - TechCorp API Refactor: 3h (merge conflicts + payment refactor)
  - TechCorp CTO response: 0.5h
  - StartupXYZ auth module: 3.5h
  - Admin: 0.5h (invoice)

  Total billable: 7h. Sound right?"
Seb: "TechCorp was more like 3.5h, I had a call too"
Morphee: "Updated. Logged:
  - TechCorp: 4h
  - StartupXYZ: 3.5h
  - Admin: 0.5h (non-billable)
  Total billable: 7.5h ✓"

Key features used​

  • Spaces (nested): Company → Client → Project hierarchy. Each level inherits parent settings but can override
  • Per-Space Interfaces: TechCorp Space has JIRA + Slack. StartupXYZ has Linear + Discord. Each project Space within a client inherits the client's tools
  • Integrations: JIRA, Linear, GitHub Issues, Slack, Discord, Gmail, Calendar, invoicing
  • Memory: Meeting decisions per client, code context per project, rates and contracts in admin
  • Skills: Morning brief (cross-client), context switch (loads the right tools), invoice generation, time tracking, meeting recall

The Space hierarchy in detail​

This is the key architectural feature for contractors:

🏢 Seb Dev (root Space)
│
│   Interfaces: Gmail (personal), Calendar, Notifications
│   Memory: company-level (rates, templates, tax info)
│
├── 💼 TechCorp (client Space)
│   │   Interfaces: JIRA (TechCorp board), Slack (TechCorp workspace)
│   │   Memory: client-level (contract, contacts, decisions)
│   │
│   ├── 🚀 API Refactor (project Space)
│   │   │   Inherits: TechCorp's JIRA + Slack
│   │   │   Memory: project-level (architecture decisions, PR history)
│   │
│   └── 🚀 Mobile App (project Space)
│       │   Inherits: TechCorp's JIRA + Slack
│       │   Memory: project-level (design specs, API contract)
│
├── 💼 StartupXYZ (client Space)
│       Interfaces: Linear, Discord
│       ...

Interface inheritance: When Seb opens "TechCorp API Refactor", he gets TechCorp's JIRA and Slack automatically — he doesn't configure them per-project. But if one project used a different tool, it could override at the project level.

Memory isolation: What Seb knows about TechCorp's architecture doesn't leak into StartupXYZ conversations. But company-level knowledge (his rates, his invoicing templates) is available everywhere.

Context switching: "Open StartupXYZ MVP" loads the right Interfaces, the right memory, the right conversation history. It's like switching to a completely different work environment with one sentence.

Why it works for him​

Freelancers don't need a project management tool. They need a context manager. The cognitive cost of switching between clients — different tools, different codebases, different people, different decisions — is enormous. Morphee eliminates that cost.

Each client lives in their own Space with their own tools, their own memory, their own history. When Seb says "Open TechCorp", he's not just switching a tab — he's loading an entire work context. The AI knows the right JIRA board, the right Slack channels, the right codebase, and what happened in last week's meeting.

The killer feature: the morning brief crosses all Spaces. One question surfaces what matters across every client, every project. No more checking 4 different Slack workspaces and 3 different project boards to start the day.

And the admin Space handles the stuff freelancers always forget — invoicing, time tracking, tax deadlines. Because Morphee already knows how many hours were spent where, it can generate invoices automatically.