BC
Brad CodyAdministrator

Future product / Delivery sequence

Build the platform in the order it becomes safe and useful.

Three foundational specifications are now released. The active release is implementation step 02: locking the shared-component system and bringing the live interface into conformance before later product modules expand.

3Released specifications
1Active release
12Queued releases
14Ordered delivery steps

Released foundation

Released specifications

Released means accepted as the current production baseline. Later work may extend these services, but it should build on their shared contracts rather than reopen or fork them.

03Released

Teammates, Teams, Role Labels & Notifications

Workspace membership, Teams, customer-defined Role Labels and the editable notification catalogue are complete for the released baseline.

Release dateAugust 3, 2026

04Released

Authenticated Workspace Dashboard & Profiles

The authenticated shell, role-aware dashboard, User Profile, Workspace Profile and shared profile architecture are complete for the released baseline.

Release dateAugust 4, 2026

Delivered outcome

Users can enter a Workspace, manage identity and organization profiles, and reach the operational product surfaces.

Open released specification →
05Released

Provider Applications & Provisioning

Designer and all nine Provider Category applications, approval workflows, pending accounts, Entity creation, Workspace provisioning and owner invitations are complete for the released baseline.

Release dateAugust 4, 2026

Delivered outcome

Approved Designers and Providers can move from website Application through review, qualification and Workspace onboarding without duplicate Entity records.

Open released specification →
Now02

Active release · Spec 16

Active

Lock Shared Components & Refresh the UI

Standardize fields, selectors, tables, forms, statuses, navigation patterns and feedback states while applying the approved interface updates across the live shell and reusable modules.

Depends onReleased Specs 03, 04 and 05 plus the current-product component and interface audit
Release gateApproved shared contracts and refreshed UI patterns exist for phone, address, money, date/time, dropdowns, grids, forms, uploaders and record modules; new work cannot create local variants.
Open active specification →

Remaining build order

One dependency-safe delivery path

The number is implementation order, not specification number. Specifications remain canonically numbered in the Product Library.

03Spec 07

Build the Project Operating Centre

Queued

Build the canonical seven-Phase Project foundation early, then add Items, Categories, Budgets, Provider Requirements, procurement, receiving, storage, delivery, installation and Project Presentations. External audience expansion remains gated by the later authentication and permissions releases.

Dependency gate

Specs 04, 05 and 16; use the existing internal access baseline until Specs 17 and 08 land

Definition of done

One canonical Project connects Client, Designer, Providers, phases, Items, budgets and operational evidence; sensitive external access remains disabled until its security gates pass.

Open Spec 07 →
04Spec 17

Harden Authentication & Account Security

Queued

Repair Google OAuth, verify recovery and email delivery, preserve invitation/application continuation, and add sessions, recent-authentication gates and MFA foundations.

Dependency gate

Specs 03, 04 and 16

Definition of done

Email/password, Google, verification, recovery and authorized destination resolution pass end-to-end security tests in every environment.

Open Spec 17 →
05Spec 08

Enforce Custom Permissions & Data Visibility

Queued

Implement customizable Access Roles, record scopes and field-level visibility for financials, contacts, Provider identity, communications and Client-facing data, including the new Project records created in step 03.

Dependency gate

Specs 03, 04, 07, 16 and 17

Definition of done

Admin, Designer, Provider and Client fixtures prove server-enforced Workspace, Project, record and field boundaries before external Project access is enabled.

Open Spec 08 →
06Spec 09

Finish Pipelines, Forms & Automation

Queued

Replace legacy Lead behavior with governed and Workspace-created Pipelines, versioned forms, transition requirements, outcomes and communication/task automations, then connect conversion cleanly into the canonical Project service.

Dependency gate

Specs 05, 07, 08, 16 and 17

Definition of done

Creation, grid, board, records, transitions and Project conversion use the same published Pipeline version; no legacy stage, LD identifier or Proper Gallery vocabulary remains.

Open Spec 09 →
07Spec 12

Add Tasks, Calendar, Resources & Time

Queued

Upgrade Tasks and Project templates with dependencies, milestones, recurrence, schedules, resources, availability, time tracking and Project calendar views.

Dependency gate

Specs 07, 08 and 16

Definition of done

Project work can be assigned, scheduled, time-tracked and capacity-checked across Users, Teams and Provider resources.

Open Spec 12 →
08Spec 14

Complete Files, Notes & Deliverables

Queued

Create versioned Files, structured Notes, comments, deliverables, decisions, evidence and an explicit Activity-versus-Audit History model.

Dependency gate

Specs 07, 08, 12 and 16

Definition of done

Every Project and record can preserve version, approval, visibility, retention and audit evidence without duplicate file or timeline systems.

Open Spec 14 →
09Spec 10

Launch Matchmaking, Offers & Assignments

Queued

Build immutable Match Runs for Designers and every Provider Category, explain rankings, govern shortlists and operate Offer acceptance, decline, counter and Assignment creation.

Dependency gate

Specs 05, 07, 08, 09 and 16

Definition of done

No stale subject can generate outreach; accepted Offers create the correct Project relationship and minimum access grant.

Open Spec 10 →
10Spec 06

Build Proposals, Work Orders, Invoicing & Payments

Queued

Add branded Designer proposals, Provider quotes, accepted scope, Work Orders, invoices, payment schedules, settlement and permission-scoped global tables.

Dependency gate

Specs 07, 08, 10, 14 and 16

Definition of done

Designer and Provider commercial journeys progress through immutable versions and auditable acceptance into operational and financial records.

Open Spec 06 →
11Spec 11

Build Communications & Unified Inbox

Queued

Connect email, SMS, calling and in-app Conversations with Project classification, internal notes, tags, assignment, purchased numbers, recordings and transcripts.

Dependency gate

Specs 07, 08, 12, 14 and 16

Definition of done

Admin, Designer, Provider and Client communication routes use one permission-safe conversation service with delivery and consent states.

Open Spec 11 →
12Spec 13

Launch the Client Portal

Queued

Give Clients a polished Project experience for approved schedule, presentations, selections, decisions, files, communications, proposals, invoices and payments.

Dependency gate

Specs 06, 07, 08, 11, 12 and 14

Definition of done

Client fixtures can complete every permitted decision and transaction without seeing internal Notes, margins or hidden Provider data.

Open Spec 13 →
13Spec 15

Add Reporting & Operational Intelligence

Queued

Create separate Registry, Designer Studio and Provider reporting with governed metrics, freshness, drilldowns, exports and scheduled delivery.

Dependency gate

Canonical records from Specs 05–14

Definition of done

Every metric has an owner, definition, lineage, permission policy and reconciliation test against source records.

Open Spec 15 →
14Spec 18

Connect the External Platform

Queued

Complete environment-governed integrations for Resend, Twilio, Google Workspace, Stripe, QuickBooks and approved Vendor or logistics APIs.

Dependency gate

Stable domain services and Specs 06, 07, 11, 12, 14, 15 and 17

Definition of done

Each integration has scoped consent, signed events, idempotency, reconciliation, monitoring, disconnect behavior and an accountable owner.

Open Spec 18 →

Roadmap governance

Rules that protect the architecture

The sequence may be refined, but these dependency and acceptance rules remain in force.

  1. 01

    Spec 16 is both a shared-component gate and a coordinated UI refresh: every later release consumes its approved components and interface patterns rather than creating local variants.

  2. 02

    Spec 08 permissions are enforced before Provider, Client, contact, communication or financial data expands to new audiences.

  3. 03

    Projects move forward early as the operational centre, but external and sensitive Project access stays disabled until authentication and permission gates are complete.

  4. 04

    Integrations are attached only after the corresponding internal domain record is stable and auditable.

  5. 05

    A specification leaves the roadmap only after its current-product gap register has closure evidence, migration results and accepted regression tests.

← Future specificationsContinue active release →