A strategic pivot from single-operator production platform to SaaS for creative producers. Same product. Different customer. Different business.
v2 sharpens the model across three dimensions: who signs up and what they see (hard access rules between Producer, Freelancer, Client), how producers charge transparently (Open Book mode), and how the platform grows from the bottom up (sequencing the flywheel).
“I don't want to produce a million projects a year.
— Roy, on the realisation
I want to do the work I love — and have the tool I built earn quietly while I do it.”
Bento OS was designed as ByBento's internal operating system. Roy runs the production company, manages clients, assigns freelancers, handles quoting and invoicing. Revenue comes from project margins (COGS + 25–30% management fee).
Roy is the bottleneck. The business doesn't scale, and it isn't sellable.
Roy is the customer, not the clients or freelancers. There are thousands of creative producers with the same problem: managing multiple clients, crews, budgets, schedules, deliverables and payments across concurrent projects.
They need the same tool Roy is building for himself.
Is “creative producer” a real category, or a hopeful hypothesis?
Real and growing. Still an emergent self-descriptor rather than a formally codified job title — which is exactly the right moment to own it.
Profiles using “creative producer” as a primary title have grown steadily since ~2019 — especially in commercial photography, branded content, and social video. The exact cohort Bento OS targets.
APA (Advertising Producers Association) and AICP separate creative producer from line producer or executive producer. The first handles concept, clients, and crew assembly. Exactly Roy's archetype.
Mid-career creatives (5–10 years in, often ex-agency) reposition as creative producers to access bigger briefs they can subcontract rather than execute alone. The career arc Roy has lived himself.
Used by practitioners in Cape Town and Johannesburg's branded content and advertising sectors — less formally than US/UK, but meaningfully. Roy's immediate network is inside this cluster.
Current stack: Google Sheets, WhatsApp groups, Dropbox, Xero. Notion and Airtable for the more organised tier. There is no purpose-built tool for this archetype. That's the opening.
Lead with “creative producer” as the aspirational identity Bento OS is built for — not just a job title, but a business model. The solo creative who runs multi-person projects. Bento OS is the operating system that makes the leap from freelancer to creative producer viable.
Same features. Different model. Compounding outcomes.
How the same code becomes a multi-tenant SaaS without rocking the boat.
You can't be a competitor and a tool provider under the same name. Three entities, three brands, three roles.
The SaaS product. Workspaces, subscriptions, recurring revenue.
The businessRoy's production and photography work, run as a sole proprietor.
Personal incomeThe legal entity that owns and operates Bento OS.
Behind the scenesByBento as a production-company brand retires. Roy doesn't need a new entity — sole proprietor under his own name handles the production work cleanly.
Each producer gets a fully-isolated workspace. Bento OS is the platform that hosts them.
Each workspace is fully isolated. Producer A cannot see Producer B's clients, quotes, or freelancers — enforced at the database via Row-Level Security.
Roy runs his production work as Workspace #1. SaaS subscription revenue is the business; production income is personal.
New in v2. Every person on the platform signs up through one of three doors — Producer, Freelancer, or Client — and sees a scoped slice. Access rules between them are enforced at the database, not the UI.
Creative producer receiving briefs and assembling teams. Solo producers (Roy-level), small production companies, and larger production studios running TVC-scale work.
Paid subscription. Own workspace.
Specialist getting booked for creative work. Photographer, editor, DP, animator, retoucher, grip, PM, coordinator. Maintains a directory profile.
Free tier by default. Pro tools Phase 4+.
The end customer who commissions work. Brand managers, marketing leads, in-house producers at agencies, event organisers, creative agencies, any org or individual putting out a brief. Works through a producer on the platform.
Internally we are sharpening this identity as "Commissioner" — Client stays the canonical public term.
Clients never access the freelancer directory. Under any circumstance. Agencies, brand teams, and in-house marketing are Clients under this rule — they pick a producer, submit briefs, receive deliverables, but the producer chaperones freelancer selection. This protects the producer's creative judgement from being commoditised out by clients who would otherwise try to book freelancers directly.
Implementation: identity_type stored on user record at signup drives workspace creation, directory visibility, and UI routing. Row-Level Security enforces the rules at the database layer — UI gating alone is insufficient.
Many creatives wear two hats. v2 adds a third: the Team Member — scoped internal staff inside a producer's workspace.
Pattern: producer upgrades a trusted freelancer to Team Member. The Team Member keeps their freelancer profile (still bookable by other producers), and gains scoped workspace access.
MVP is deliberately tight. Hard rules are never tunable. The middle ground (quote totals, rate cards, freelancer fees) needs scoping per producer feedback in Phase 2–3.
Clients are not dual-role. They commission work, they don't execute it. If Roy commissions Thoban for a personal shoot, he operates through his Producer workspace engaging another Producer, not a Client workspace. Mixing identities would break the access rules.
Cleanest pattern for Producer + Freelancer toggle (Uber driver/rider, two linked profiles, context-dependent views)? And Team Member permissions: role-based vs attribute-based access control?
New in v2. Producers classify on two orthogonal axes. One is commercial, one is discovery. They are independent.
What the producer pays ByBento and what features they can access.
How producers surface in the directory. Self-declared. Not tied to subscription. Not a pricing axis.
The two axes are independent. A Solo-subscription producer can be a Top-tier by job experience (a TVC-capable producer who keeps their tooling lean). A Pro-subscription producer can be a Mid-tier by job experience. Verification of job-type tier (verified Top unlocks discovery boost) is TBD Phase 3, after soft-launch feedback.
Note on "Pro Plus": v1 called this tier "Agency." v2 renames it — in the SA creative industry, "agency" reads as the Client identity (creative agencies = clients, not producers). Pro Plus is a working name. Pro Team is the other candidate.
Free to list. Five visibility modes per freelancer. Tier-gated access per producer.
v1 assumed a per-booking fee would be charged to freelancers. v2 removes that assumption. Directory listings are free by default. Freelancer-side revenue is reframed as a paid-tier product (Freelancer Pro Tools, Phase 4+) — a product upgrade for professional tools, not a tax on supply.
The platform becomes something freelancers pay for because it makes them better at their craft and business, not because they're forced to route bookings through it.
Any producer (subject to producer's tier-based directory access).
Only producers at specified subscription tier(s), e.g., "Pro and Pro Plus only."
Only producers the freelancer has explicitly approved.
All producers except ones on the freelancer's blocklist.
No producers. Profile inactive in search, still functional for existing bookings.
A successful match: the producer can see the freelancer (tier + visibility mode both permit it) AND the freelancer is bookable (not Hidden, not at capacity). Both sides control their end. The platform mediates via RLS policies.
The flywheel has two sides — producer ↔ freelancer and producer ↔ client — but they don't both activate simultaneously. v2 sequences the rollout bottom-up: supply side matures first (freelancers + Solo producers), then demand side plugs in (Pro producers → Pro Plus feature set → client-side activation via Open Book + Brief Marketplace). See rollout section for detail.
New in v2. A distinct mode of working between a producer and their client, enabled once the producer base includes credible higher-tier producers whose creative judgement is the visible value on offer.
"I don't want to hide my margin. I want the client to see that what they're paying me for is the judgement call on which DP, which editor, which day."
— The mode that lets premium producers charge transparently
Opt-in per project. Default stays closed-book. Producer decides who to offer it to.
Unblocks once Pro Plus tier ships at Phase 4.
Phase 5 Savings Share sublayer. Mobile Media Mob origin. Client sets a budget ceiling, producer delivers under, parties share the savings. Earns its spot once core Open Book is validated with real producer/client pairs. Not MVP. Not Phase 4. Phase 5 at earliest.
Does Open Book apply at quote-build time only, or continue through execution (every change re-priced live)? Can producers offer it selectively (some clients yes, some no) or is it per-project? Does the platform take a cut of Open Book transactions, or is it just a UX layer?
What's in the build. What stays the same. What changes. Where the boundaries are.
Core features carry across. v2 adds six concrete change areas over v1.
producer_markup_pct visible on profile — trust signal + prerequisite for Open Book mode.v2 additions over v1 add roughly: identity/access-rule hardening, producer markup primitive, brief marketplace scaffolding (post-MVP), job-type tier field, Team Member role, beta feature flags. Most are additive fields and RLS extensions, not structural changes.
Bookem-level invoicing, not full accounting. Producers quote, invoice, and track payments inside the platform.
Why not? Handling other people's money in SA requires being an authorised financial service provider. Different industry, different regulations, different liability. Hard no.
Reference product: Bookem ↗ — SA practice management software with similar invoicing scope and customisation model.
Four tiers. Solo + Pro + Free at MVP. Pro Plus unlocks at Phase 4, feature-gated not calendar-gated.
Freelancers who want to be listed and receive jobs
Independent creative producers with their own clients
Small production companies and busy creative producers
TVC-scale operations, multi-producer teams, production studios
Pricing is illustrative. Early signal from SA producer conversations (April 2026): R500/mo reads as "easy spend" to the target. Formal validation needs 5–10 producers trying the product end-to-end. "Pro Plus" renames v1's "Agency" tier — in the SA creative vernacular, "agency" reads as the Client identity (creative agencies = clients, not producers).
The good news from the technical audit. The numbers. The path forward.
A deep audit of the current Bento OS 5 codebase revealed something unexpected.
workspaces table
Producer accounts sitting above client companies
workspace_id to ~8 tables
Scope packages, quotations, inquiries
identity_type on user record
Routes signup into Producer / Freelancer / Client; drives UI + RLS
producer_markup_pct on producer profile
Declared markup %; feeds Open Book + trust surfacing
job_type_tier on producer profile
Solo / Mid / Top — directory discovery axis
freelancer_visibility_mode + allowlist / blocklist tables
Five modes (Open / Tier-filtered / Allowlist / Blocklist / Hidden) + many-to-many mappings
workspace_role for Team Members
Scoped permissions per feature (read-only start; Pro tier and above)
feature_flags + user_feature_flags tables
Beta feature rollout; Roy as User #1 dogfooding
+2–3 weeks over the v1 baseline; v2 additions over v1 add roughly +1 week for scaffolding (identity + markup + visibility + workspace_role + feature flags). Most v2 additions are additive fields and RLS extensions, not structural changes.
One confirmed for MVP. Two deferred to Phase 4+. Production revenue is linear. SaaS revenue compounds.
Primary revenue stream. Producers pay monthly. 4 tiers: Free / Solo (R499–R799) / Pro (R1,499–R2,499) / Pro Plus (TBD). Predictable, compounds with growth. 80–90% gross margin.
Year 1 target: 30–50 paying producers — the "platform funds itself independently of production work" threshold.
When a client posts an open brief on the platform and a producer wins it, ByBento takes a commission on the booking. Platform-sourced briefs only. Projects a producer brings from their own network are subscription-only, no commission.
5–10% placeholder. Benchmark against Fiverr (~20%), Upwork (~10%), agency lead-gen (10–15%) before Phase 4 spec.
v1 assumed per-booking fees. v2 removes that and reframes Stream 3 as a paid-tier product for freelancers who want professional tools to manage their freelance business — closer to how Notion or Dropbox charge individuals for pro features. Not a tax on supply; a product upgrade.
Candidate features: availability calendar + Google/Outlook sync, quote templates, CRM-lite for own direct clients, invoicing for off-platform work, expense tracking, portfolio showcase pages, auto-payout tracking, earnings analytics, priority directory surfacing, AI assistant for rate setting and contract drafting.
Launch gate: Stream 1 validated with 50+ producers and 500+ freelancers on Free tier before this stream activates. Target R199–R399/mo. Freelancers are ~10× more numerous than producers — this stream roughly doubles addressable market.
Production revenue is linear (more work = more money, max hours in a day). SaaS revenue compounds. After 12–18 months of moderate growth, Stream 1 alone could significantly exceed what production work could ever deliver. Streams 2 and 3 are the delta that separates "replace production income" from "meaningful SaaS business."
Five phases. The two-sided flywheel (producer ↔ freelancer and producer ↔ client) doesn't activate simultaneously — supply side matures first, demand side plugs in once credibility is established. Each phase earns the next.
Why this sequencing: the platform can't pitch Pro Plus tier to a TVC-scale producer until the Pro Plus feature set exists. It can't activate Brief Marketplace until the producer base has credibility. It can't offer Open Book mode until higher-tier producers are present to justify the transparent-premium framing. It can't charge freelancers for Pro tools until there's a critical mass of bookings flowing. Each phase creates the conditions for the next.
Naming the things that could go wrong, and how we handle each.
Early signals positive but not yet validated demand.
→ Three independent conversations with SA producers in Roy's network (Apr 2026) produced consistent positive reactions — including "R500/mo is an easy spend." Lightweight, not validated. Formal validation: 5–10 producers trying the product end-to-end.
CTIJF, Defender Trophy, photography website, ROYS_OS, Bento OS — Roy's bandwidth is real.
→ Don't acquire external users until Roy has run 3–5 real projects through the platform. Launch = Roy using it.
Data leaking between workspaces would be catastrophic. v2's per-identity-per-feature rules make the refactor denser still.
→ Comprehensive test suite: User A cannot see User B's data, Clients cannot see freelancer directory via any UI path or direct query. Mindlink advises on RLS refactor approach.
+2–3 weeks vs v1 baseline; v2 additions add ~1 week for scaffolding.
→ Workspace layer is additive. v2 adds mostly fields + RLS extensions, not structural changes.
Real once Stage 3 ships. Some clients will use transparency to push for cheaper freelancers or question every producer choice.
→ Open Book is opt-in per project; producer can decline to offer it per client; platform tracks which clients abuse the mode (reputation signal).
Real if Pro Plus is launched prematurely. Producers evaluate tiers against feature depth; premium price without premium feature set creates churn.
→ Pro Plus launches only when Stage 3 producer-portal features are live. Feature-gated, not calendar-gated.
Onboarding UX, support, docs, billing management — all new work.
→ Defer all of it to post-MVP. First version: invite-only, Roy + 5 friends.
Producer + freelancer profiles plus scoped Team Member permissions add UX and data model complexity.
→ Get Mindlink's recommendation on both patterns before building. Start Team Member permissions tight; loosen on feedback.
First guess is usually wrong.
→ Start with Free + one paid tier. Iterate from real usage. Early signal: R500/mo reads as "easy spend" to target producers.
Platform does not handle producer-client money.
→ Producers collect their own payments. Platform only collects subscription fees.
What changes for Mindlink in v2, what doesn't, and the four architectural questions we need a recommendation on.
"v2 of the pivot plan sharpens v1 without breaking it. Same three identities — Producer, Freelancer, Client — now with hard access rules (clients never see the freelancer directory). Producer markup becomes a platform primitive. Client portal evolves in stages tied to overall platform maturity. Pro Plus tier unlocks at Phase 4, gated on feature set not calendar. Three revenue streams — subscriptions confirmed for MVP, Brief Marketplace commission at Phase 4, Freelancer Pro Tools at Phase 4+. Rollout is deliberately bottom-up — supply side first, demand side activates once producer base has credibility."
— The 30-second v2 pitch
workspaces table and scope all data to workspacesidentity_type field on user record + three-door signup routingproducer_markup_pct + job_type_tier on producer profilefreelancer_visibility_mode + allowlist/blocklist tablesworkspace_role table for Team Member scoped permissionsWhere we need your architectural recommendation before building. v2 expands from three to four — Team Member permissions and directory performance are new.
We need to replace ~47 RLS policies that currently use global is_admin() with workspace-scoped, identity-aware policies. v2 adds: Client cannot see freelancer directory (enforced per-table, per-query), Team Members have scoped permissions per feature. What's the safest refactor approach? What testing pattern verifies isolation and prevents cross-identity data leaks?
Roy (and many users) need to be both a producer (paid workspace, manages clients) and a freelancer (listed in directory, gets booked by other producers). What's the cleanest architecture? Single account with role toggle (Uber driver/rider)? Two linked profiles? Context-dependent views based on workspace? This affects the data model, auth flow, and UX.
Team Members need scoped access inside a producer's workspace (project ops, talent confirmation, call sheets — but never profit margins, client payments, or billing). Hard rules are never tunable; middle-ground rules (quote totals, rate cards, freelancer fees) need to be easy to loosen over time. Role-based access control (RBAC) vs attribute-based (ABAC)? Which fits better with Supabase RLS + our feature set?
v2's directory query composes producer subscription tier + freelancer visibility mode + allowlist/blocklist + job-type filters, potentially across a large freelancer table. How do we structure the query so Solo and Pro tiers get fast results at 500–5,000+ freelancers without index pain? What's the safe pagination + filter pattern?
For reference. These are locked. v2 additions marked.
producer_markup_pct declared on profile, visible to clients. Trust signal + prerequisite for Open Book.