01 / Qualify and scope
Agree on the problem, accountable stakeholders, systems in scope and the deliverables. A discovery call or draft email is not an accepted engagement.
New clients / Secure delivery
A clear path from first conversation to engineering handoff.
Each engagement has an agreed scope, responsible contacts, access boundaries and acceptance criteria. The invitation-only project workspace exists in code, but private services are not presented as active until identity and storage are configured.
How the onboarding sequence works
02 / Contract and authorize
Sign the applicable agreement and scope, verify NDA/data handling terms, and approve any security testing or production access.
03 / Grant least-privilege access
Exchange credentials through an approved secure channel, never an open intake form. Use identity, tenant membership and time-bound access appropriate to the work.
04 / Review milestones and handoff
Use approved milestones, test evidence, change history, acceptance decisions and revocation of access at closeout.
Private workspace activation
The platform supports tenant membership, project messages, approved milestone updates, two-party scope decisions and private documents. Access requires Cloudflare Access identity verification, a correctly provisioned D1 database, private R2 storage and an approved invitation. It is not a public document upload form; no credentials, customer files or confidential project details should be emailed with an initial inquiry.
View private workspace activation statusClient workspace / Illustrative view
See the project, evidence and sign-off in one place.
This is static example data, not a customer record or live demo account. The real portal code supports tenant-scoped projects, milestones, secure files, messages and two-party approvals, but customer access remains disabled until independent identity, R2 storage and invitation checks are completed.
Example: accepted
01 / Scoped discovery
Authorized scope, owners and acceptance criteria
Example: in review
02 / Prototype and tests
Versioned deliverable, test trace and known limitations
Example: planned
03 / Release and handoff
Change approval, rollback instructions and access revocation