Brendan/boundhq
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Save strategy, readiness and audit docs from inbound media

Browse Source
This commit is contained in:
Brendan
2026-06-14 02:11:12 +00:00
parent 87d6cc14ec
commit a6f28668d3
15 changed files with 1436 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
inbound/CUSTOMER_ONBOARDING_BLUEPRINT.md
+68
View File
@@ -0,0 +1,68 @@
# Customer Onboarding Blueprint
This blueprint defines the ideal first-customer onboarding flow and assesses current support. The recommendation is a "Do It For You" first customer onboarding path, with self-serve wizard deferred until the manual path is proven.
## Onboarding Principles
- First customer should reach first quote/invoice fast.
- Brendan should not need to explain database concepts.
- BoundHQ can manually configure risky/technical steps.
- Every step should be skippable unless it blocks quoting, invoicing, or legal compliance.
- Capture state, setup owner, and verification result for each step.
## Wizard Flow
| Step | Required? | Current support | Can skip? | DIFM fit | Notes |
|---|---|---|---|---|---|
| 1. Create tenant | Required | SaaS Admin staging; tenant CLI proven | No | BoundHQ only | Must run tenant smoke test |
| 2. Admin user invite/set password | Required | Auth/invite routes exist | No | BoundHQ can create | Login bounce must be fixed |
| 3. Company details | Required | `/api/business/me`, Settings Appearance | No | Either | Business name, ABN, address, state |
| 4. Compliance state | Required | Compliance service exists | No | BoundHQ recommended | Drives deposit caps and terms |
| 5. Logo/branding | Optional | Business logo upload exists | Yes | Either | Can use plain template first |
| 6. Users and roles | Required for team | Settings users/module access | Yes for solo | Either | Start with owner/admin |
| 7. Numbering | Required | Numbering settings exist | No | BoundHQ recommended | Quote/job/invoice prefixes |
| 8. Pricelist setup | Required | Pricelist import/manual exists | No | Strong DIFM | Starter pack plus CSV import |
| 9. Quote template | Required | PDF template UI exists | No | BoundHQ recommended | Must be compliance-safe |
| 10. Invoice template/profile | Required | Invoice profiles/templates exist | No | BoundHQ recommended | Deposit/final invoice path |
| 11. Xero connection | Strongly required | OAuth exists but scopes blocked | Can defer manually | Customer + BoundHQ | For Stage 1, decide manual fallback |
| 12. Tradify import | Optional but high value | Importer staging | Yes | Strong DIFM | Use after core setup |
| 13. Email parsing setup | Optional | Email Intake staging | Yes | BoundHQ recommended | Needs IMAP/OpenAI/privacy consent |
| 14. OneDrive/file storage | Optional | File paths/rclone architecture | Yes | BoundHQ only | Later unless customer relies on drawings |
| 15. Job stages/workflow | Required | Jobs board exists | No | BoundHQ recommended | Start with default cabinet workflow |
| 16. SMS setup | Optional | Twilio built | Yes | BoundHQ only | Tenant-specific sender/costs later |
| 17. AI feature opt-in | Optional | Email AI exists | Yes | BoundHQ | Privacy language needed |
| 18. First project setup | Required | CRM/quote/project/jobs exist | No | Joint | Create one real customer/job |
## Minimum Manual Onboarding Checklist
1. Provision tenant and owner account.
2. Confirm login works.
3. Enter business details, ABN, address, state, timezone.
4. Set module access to Stage 1 modules only.
5. Configure numbering.
6. Load starter pricelist or customer CSV.
7. Configure quote/invoice templates and state terms.
8. Create one customer and one sample quote.
9. Generate quote PDF and verify legal terms.
10. Accept quote through public portal.
11. Confirm project/job/deposit invoice are created.
12. Connect Xero or record manual accounting fallback.
13. Train owner on daily loop: customer -> quote -> job -> invoice.
## Self-Serve Wizard Later
The self-serve wizard should only be built after the first DIFM onboarding is completed. It should store onboarding progress in a future table such as `onboarding_steps` or `business_onboarding_status`, but no schema change is recommended during this audit.
## What Brendan Should Do Personally
- Identify the first customer.
- Decide if Xero setup must be live before onboarding or can be manually assisted.
- Validate the first customer can understand the quote/job/invoice loop.
## What AI/BoundHQ Should Do
- Provision and verify tenant.
- Configure defaults.
- Import starter data.
- Produce a one-page customer quick-start.
- Capture every manual setup step as future wizard requirements.