The honest boundaries for Early Access.
These notes are here to keep trust high. Early Access should feel supported and useful, not overpromised.
Access is intentionally limited
New accounts require an invite code while the first operators validate the workflow. Capacity should expand only after the core flow and support loop are stable.
Founder-led support
Support runs through support@handymansfriend.com and the signed-in feedback form. Response targets are internal operating goals, not a public SLA.
Project workflow hardening is active
The Project model is the right direction, but request-to-payment paths still need real-world validation across old and new records.
Payments and public links get priority
Anything involving login, Stripe, invoices, quotes, payment links, or customer-facing documents should be reported immediately.
Native iPhone work is not the launch blocker
Mobile web remains the primary field-ready surface for Early Access. The native iPhone app is a companion track and should not outrun the web product.
Some workflows may still require help
Normal operator workflows should be straightforward, but edge cases around billing, Connect onboarding, and recovery actions may need founder support.