/01
Client-owned accounts
Production hosting, database, email, analytics, payment, and AI-provider accounts are set up under the client when the project requires them.
← BACK TO HOMEBUILD THE PRODUCT
/SECURITY + HANDOFF
BUILD THE PRODUCT
WITHOUT LOSING CONTROL.
Custom software should not trap your data, source code, vendor accounts, or operating knowledge inside a developer relationship. The engagement is scoped so the client can own the system after launch.
/02
Least-privilege access
Admin roles, participant links, exports, and internal tools are scoped so people see only what they need.
/03
Sensitive-data boundaries
Assessment responses, HR-style records, patient intake, payment data, and customer records are treated as first-class product constraints.
/04
No source-code hostage situation
Handoff includes the repository, deployment notes, environment-variable map, and enough documentation for another developer to continue.
/CLIENT OWNS
NO HOSTAGE
HANDOFF.
Source-code repository
Cloud and vendor accounts
Database and production data
Deployment configuration
Environment variable map
Project-specific IP
/SCOPED BEFORE BUILD
THE SECURITY MODEL IS PART OF THE PRODUCT SCOPE.
Data sensitivity
Which fields are personal, confidential, regulated, client-owned, exportable, or safe to keep out of the product entirely.
User roles
Who can create records, invite participants, view responses, approve reports, export data, or administer accounts.
Vendor boundaries
Which services touch email, storage, analytics, AI, payments, PDFs, or notifications, and whose account pays for them.
Handoff path
What must exist for another developer to continue safely: docs, repo access, deploy steps, schema notes, and account ownership.
BUILDING SOMETHING SENSITIVE?
Bring the workflow, data types, user roles, and current manual process. The discovery call will separate product scope from data and access decisions before any quote is final.
BOOK A SECURITY-MINDED BUILD CALL