15-minute bug fixes
Small eligible bugs are fixed within 15 minutes once we can reproduce them and have the access required to ship safely.
Larger incidents enter the agreed severity path.Software that fits the operation.
Caldrin builds the home-services workflows generic SaaS leaves unresolved, then stays close enough to fix, change and improve them without a vendor queue.
Software transformation at 603
Before · separate toolsOperating layer · current state
Builder Prime
Custom CRMAudited migration
NiceJob
Review workflowBuilt, switches off
ArcSite
ArcSite integrationKept + integrated
Resend
AWS SESActive paths moved
Fast fixes. Direct access. No per-seat tax.
Fast changes matter only when the boundaries are clear. The headline stays simple; eligibility, access, acceptance and incident severity are agreed before work begins.
1-hour feature requests
Have a small, bounded idea at 2am? Send it. The target is to have it shipped within an hour.
Larger requests move into a visible priority queue.Unlimited 24/7 support
No support tier. No enterprise-support upsell. The people building the system stay close to the people using it.
Fair-use and emergency boundaries are agreed in writing.$0 until it works
You do not pay until the agreed software passes its acceptance criteria and the agreed user group is using it.
Scope, access, onboarding and acceptance are defined before work starts.Operator-led onboarding
You are onboarded with someone who understands leads, inspections, estimates, jobs, field teams and follow-up.
Not handed to a generic implementation queue.No per-seat tax
Adding a salesperson, location or acquisition should not automatically increase the software bill.
Commercial terms are set around the operating model, not user count.The 15-minute and 1-hour targets apply to eligible, reproducible, bounded requests. They are not a promise that every production incident or arbitrary enterprise feature is fully resolved inside that window.
Keep the familiar workflow, or remove everything the team works around.
The right migration is not always a clean-sheet redesign. Choose the mode that gets the operating team to a useful system with the least avoidable disruption.
Same workflow. Less retraining shock.
Preserve the information architecture and interaction patterns the team already knows, where technically and legally appropriate.
- Lower perceived change
- Faster adoption
- Familiar sequence and records
Keep what works. Kill the bloat.
Rebuild the workflow around what the team actually uses and remove unnecessary screens, clicks and workarounds.
- Fewer steps
- Clearer controls
- Only the exceptions that matter
Built from problems inside a home-services business.
Nik Mellett brings the 603 Basement Solutions owner/operator perspective to the leads, estimates, field work and follow-up behind these builds. The workflows exist in the 603 CRM codebase, but they do not establish adoption, review growth, close-rate improvement, revenue or EBITDA impact.
Review requests with gates
The leak: Review generation fails when it depends on somebody remembering to ask.
The system: A completed job creates a foreman-readiness request before the customer sequence can begin.
Built · sending controls remain off until activationSignatures inside the workflow
The leak: A disconnected signing tool creates another handoff and another status to chase.
The system: Reps prepare, send and track a private proposal-signature request inside the CRM.
Implemented · production transaction not claimed hereRequired field photos
The leak: Before and completion photos get missed when documentation is optional.
The system: Daily field reports cannot close until the required photo and finish-time gates pass.
Implemented workflow gateProposal timing you can see
The leak: Managers cannot fix follow-up they cannot see.
The system: The system records proposal sent time, rep, elapsed time, follow-up activity and overdue state.
Implemented with Gmail read-only evidenceTasks with an owner and due date
The leak: Critical work disappears when it lives in memory or a private inbox.
The system: Tasks carry an owner, priority, due date, completion state and overdue visibility.
Implemented across project and customer recordsAutomated completion check-ins
The leak: A manager should not need to chase the field team one person at a time.
The system: Scheduled SMS prompts collect job-completion answers and surface missing or conflicting responses.
Implemented · customer satisfaction uplift not claimedSources: Siteboard review campaign, proposal signing, field-photo, proposal monitoring, task and job-completion implementations · repository state inspected September 27, 2026. Production use is not claimed unless stated.
Do not buy another workaround.
The traditional SaaS model is useful when the workflow is genuinely standard. The drag begins when the operation keeps paying to bend itself around the product.
- Per-seat pricing
- Generic workflows
- Feature bloat
- Support queues
- Roadmap dependency
- Disconnected integrations
- Operating-model terms
- Only the workflows that matter
- Operator-led onboarding
- Direct build access
- Owned data and workflow logic
- White-glove migration and reconciliation
Migration is a controlled reconciliation, not a file upload.
We own the migration process until the agreed data reconciliation passes. The customer validates the mapped records and exceptions before acceptance.
Source exportMappingMigrationReconciliationCustomer acceptance
Names for the costs teams learn to tolerate.
Not every platform creates every tax. These are the recurring patterns that tell us a workflow may be worth owning.
Seat tax
Paying more because you hired another employee.
Feature bloat
The pile of unused features customers still fund.
Implementation fee
Paying extra to configure the software you already bought.
Support tier
Paying more so somebody answers faster.
Integration tax
Buying another tool because two tools you already bought will not talk.
Acquisition tax
Buying another company and inheriting another stack, migration and licence structure.
Vendor lock-in
Your data is yours until you try to leave.
Roadmap
Where a workflow-specific request waits behind requests from unrelated customers.
Workaround
The process employees invent because the system does not fit the business.
Professional services
Paying the vendor again so its software can resemble your operation.
Enterprise pricing
Contact sales.
Bring us the workflow your team works around.
We will map the users, records, exceptions and acceptance test before recommending configure, integrate, clone or rebuild.