AI and automation, custom software, and websites, scoped by people who have run the operations they change.
Intake, documents, follow-ups, and routine reporting drafted, sorted, and checked with AI, with a person approving what matters.
Custom tools, dashboards, and QuickBooks or CRM integrations for the decisions that spreadsheets and disconnected apps make difficult.
Service websites and storefronts that explain the offer and connect enquiries or orders to the people doing the work.
Start with a focused diagnostic, go straight to a scoped build, or bring us in as ongoing operations and technology leadership.
A focused review of one area of the business, with an agreed duration and a prioritized next-step plan.
A scoped project with a fixed outcome: new system, storefront, workflow, or product delivered in visible weekly demos.
Monthly operations and technology leadership: roadmap and vendor decisions, process fixes, hiring support, and steady systems improvement.
Same company, built for owner-operated businesses without an operations person: one workflow at a time, in plain language.
You do not need a polished brief. These are the details we work through before a build begins.
Digital Refraction works with growing teams whose tools and handoffs no longer fit the work. LocalCare is the same business, with a smaller scope for owners without an operations team.
Your proposal will name the person responsible for delivery and your day-to-day contact. We agree who needs to review decisions before work starts.
Yes. Start with the existing website, spreadsheet, or app. A configuration change or an off-the-shelf tool may be enough; custom software is useful when the missing workflow justifies it.
One defined problem, agreed deliverables, review points, and a handoff. The proposal separates included work from additions such as more pages, integrations, data cleanup, or ongoing content changes.
The size of the workflow, number of pages or integrations, condition of the data, content readiness, and review time. We agree the price and schedule for the specific scope before starting; a small fix and a full website are different projects.
Hosting, domains, paid tools, email services, and AI usage can have recurring charges. The proposal identifies which are needed, who pays for them, and whether support or future changes are separate.
Before starting, we document account ownership, access, the rights to content and custom code, third-party licences, and available data exports. The handoff should make clear what you can keep, move, or maintain elsewhere.
The agreed support plan sets out its duration, included fixes, contact method, response hours, and how extra work is priced. Launch support is not an unlimited maintenance subscription.
A person who can make decisions, examples of the current work, approved content, and access through an appropriate account invitation. We agree review dates and dependencies before setting the launch date.
A 20-minute call is enough to tell whether this should begin as a diagnostic sprint, a scoped build, or fractional support.