Weekly sync with Karly and Sebastian to kick off structured testing of the Hazard OS app (hazardous.app) and resolve a Microsoft Clarity setup blocker for PaperTube. The call also surfaced a significant architectural decision: replacing the current "Customers" tab with a full CRM module to better support B2B account management.
Attendees: Sebastian Gant, Karly Oykhman, Mark Hope
Testing is divided by module to avoid overlap, with findings logged in a shared Google Doc ("Hazard OS App Build") in the Advanced Health and Safety > Projects > Hazard OS drive folder.
| Person | Assigned Modules |
|---|---|
| Karly | Estimates, Invoices, Calendar |
| Sebastian | Customers, Jobs, Settings |
| Mark | Site Survey module (fixing, not testing) |
[name]+hazardos@asymmetric.app for email filtering.The existing Customers tab was modeled loosely on MarketSharp but is insufficient for B2B use cases (e.g., property management firms with multiple contacts per account).
Proposed structure (HubSpot-style):
- Accounts — company-level records (e.g., Garcia Property Management)
- Contacts — individual people linked to accounts
- Opportunities — pre-job pipeline tracking
- Jobs — existing module, linked from CRM records
Additional CRM requirements discussed:
- Clickable company names linking to account pages
- Inline action buttons (Send Email, Send SMS, Call) rather than bare hyperlinks
- Notes section surfaced prominently
- SMS logging (infrastructure already built into the app)
- Lead source tracking
- Role-based access (technicians should not see CRM tab)
Next step: Karly to write a CRM spec (fields, tabs, clickable links, SMS/email/call, notes) and send to Mark to build.
The Shopify integration was stuck on "pending project admin approval." Root cause: the approval email was sent to team@ (not a personal inbox), so it went unnoticed. Mark approved it from the team account; integration is now live.
Parag (parag@papertube.co) has been invited as a user to the PaperTube Clarity project. Data takes 2–3 days to appear.
Key lesson: When Shopify sends a "project link request," the approval email goes to the team@ account — always check there first.
The full job lifecycle as designed:
Lead → Customer → Site Survey (mobile) → AI-Generated Draft Estimate
→ Office Review & Approval → Approved Estimate → Sent to Client
→ Client Approval → Job Created → Resources Allocated
→ Job Completed → Completion Report → Invoice → QuickBooks
Settings modules available:
- Pricing (labor rates, equipment rates, materials, disposal costs, travel/mileage)
- Team (roles: admin, manager, supervisor, worker)
- Notifications (who gets notified for what events)
- Appearance / white-label (logo, colors, company name)
- QuickBooks integration (planned)
- Document Customization (identified as missing — needs to be added)
Approval workflow is configurable per job type (e.g., mold jobs may route to Brady vs. Bob).
team@ account (@Karly Oykhman)