01
Operating core
Brands and pipeline, projects and tasks, finance and invoicing, basic automations and notifications.
OrbelithExplore the productProduct delivery case study
Building Orbelith
CRM product delivery and workflow automation — from agency pain points to a connected, multi-tenant operating system.
- Role
- Project Manager / Product Owner
- Period
- 12 May–8 August 2026
- Product
- Self-initiated SaaS
- Status
- Deployed and validated
01 — Overview
One product, one connected client lifecycle
Orbelith is a multi-tenant CRM and operations platform for marketing agencies. It connects client acquisition, project delivery, approvals, finance, team operations, reporting, and scheduled automations.
Ownership
This is a self-initiated product owned by the author. The case documents direct product ownership without claiming an external client or a large delivery team.
Responsibilities demonstrated
Product definition and scopeWorkflow mappingMVP prioritizationDelivery sequencingRequirements refinementProduction feedback analysisRelease validation
02 — Product problem
Disconnected tools break the handoffs
A marketing agency often manages the same client across a sales pipeline, task board, content approvals, inboxes, spreadsheets, finance records, HR tools, and reporting templates.
The challenge was not simply to add more modules. It was to make each module support a shared client lifecycle so that context survives every handoff.
The product also had to preserve organization-level access boundaries while remaining usable across roles, currencies, and three interface languages.
Product objective
- 01Move a lead through negotiation and proposal.
- 02Organize an active client into delivery projects.
- 03Plan project work through tasks and workload.
- 04Move client-facing work through approval.
- 05Connect approved delivery to invoicing, reminders, payment, and reporting.
- 06Apply roles, localization, security, and auditability across the workflow.
03 — Scope and prioritization
Sequence the operating core before scaling breadth
The roadmap was organized around product gates: connect the essential lifecycle first, establish tenant safety, then deepen collaboration and harden production behavior.
02
SaaS foundation
Organizations and memberships, tenant-aware data, row-level isolation, and public agency signup.
03
Workflow depth
Capability-based access, approvals, client portal, team collaboration, HR, workload, and scheduling.
04
Reliability and validation
Integration hardening, private documents, currency and date correctness, production QA, fixes, and retesting.
04 — Workflow design
Design around handoffs, not isolated screens
Sales creates the context for delivery; delivery approval creates the context for finance; reporting closes the loop with the client.
05 — Delivery roadmap
Five decision gates from operating core to validation
Each phase unlocked the next one only after its core product risk was addressed.
06 — Product evidence
A live workspace, not a concept prototype
The delivered product includes pipeline, projects, tasks, approvals, workload, inbox, finance, reports, HR, scheduling, profitability, settings, and audit surfaces.
Project delivery workspace
Status, progress, budget, tracked hours, and overdue work in one operational view.
Workflow automation
Six active rules with execution state, failure visibility, and organization-scoped behavior.
07 — Key decisions
Product discipline behind the feature set
Workflow before breadth
The lead-to-invoice journey had to connect before expanding the module set.
Security before scale
Organization isolation and access capabilities became gates for broader SaaS use.
Evidence before claims
Production findings were converted into fixes and focused regression checks.
08 — Outcome
A deployed multi-tenant CRM
The result is measured through delivered product behavior and verified implementation — not unsupported revenue, adoption, or team-size claims.
- ✓Connects the client lifecycle from lead to invoice.
- ✓Combines sales, delivery, finance, and team workflows.
- ✓Isolates organization data and controls capabilities by role.
- ✓Supports English, Romanian, and Russian interfaces.
- ✓Runs six active automation rules in the demo workspace.
- ✓Completed a focused production QA loop with five fixes passing retest.