Phase 1
Discover and preserve
Confirm the business, users, current tools, required records, workflow, risks, approval owners, data sources, existing URLs, and anything that must not be replaced or lost.
Implementation that produces a working system
Configuration, verification, training, and launch—not just account activation.
Highway 38 implementation turns the selected product into a controlled working environment for the business, its users, its records, and its real workflow.
Protected launch rule
No customer message, approval, scheduling commitment, purchase, payment movement, payroll action, tax filing, or production deployment is treated as automatic unless that exact workflow is separately approved and verified.
Four controlled phases
A documented path from current workflow to accepted production use.
Phase 2
Configure and migrate
Set branding, company settings, users, roles, templates, price-book items, forms, folders, workflow rules, controlled integrations, and approved data imports.
Phase 3
Verify and train
Run structural checks, sample records, role checks, mobile and desktop checks, save-and-reopen tests, document/PDF tests, backup checks, and staff walkthroughs.
Phase 4
Launch and hand off
Move the approved configuration into production, preserve rollback evidence, confirm the live deployment, document owner controls, and identify the next review point.
Setup is included
Every plan includes onboarding — no separate setup fees.
There is no $499 assisted-setup fee and no $2,500 implementation charge. Your plan covers getting you running.
Business setup
Business and user setup tools
Quote templates and price-book structure
Business branding and company settings
Guided use of customer, quote, attachment, approval, and PDF features
Business Office onboarding
Business configuration and workspace setup
Users, roles, permissions, and owner controls
Customer, quote, job, document, money, and approval workflow configuration
Standard templates and Universal Smart Import for approved existing business data
Mobile and desktop acceptance checks
Training, launch evidence, and owner handoff
Deeper configuration
Migration, specialized modules, advanced workflows, customer or employee portals, forms, dashboards, custom permissions, approved integrations, field-capture tools, and business-specific AI are scoped and quoted separately — confirmed in writing before work begins.
Acceptance evidence
A launch is complete only when the exact production system is checked.
Functional evidence
Sign-in, role access, record creation, save and reopen, edits, attachments, PDFs, approvals, logs, backups, and controlled-action behavior.
Deployment evidence
Exact source commit, deployment run, production URL, preserved deployment identifiers, rollback reference, and live verification.
Owner acceptance
Technical checks do not replace the owner’s review of appearance, workflow fit, wording, permissions, and readiness for real business use.
Know what will be configured before paying for implementation.
Nothing is activated or charged from the request form. The product level, implementation scope, payment points, responsibilities, and launch criteria are confirmed first.