How we work. Built to protect you, designed to ship fast.
Six steps from first call to working system. Every contract has a locked-in delivery date and a guarantee that earns you the second half only when we hit it. Most builds ship in 2–8 weeks. Bigger multi-system builds, 8–12.
Six steps. Same every time.
The short version we tell prospects is three steps — discover, build, launch. The full contract version is six, and it’s laid out below. No surprise scope changes, no surprise pricing, no surprise delivery dates. You see every step before you commit to any of them.
Free Automation Audit
You book through the calendar. We have a real 20-minute conversation about your business — where time disappears, what your team does manually, what’s stuck. By the end, we’ve named 2–3 things worth automating first.
Cost: nothing. Commitment: 20 minutes. No slides, no pitch.
Honest assessment
After the audit, we tell you the truth. Sometimes the answer is “automation isn’t worth it for what you’re describing — here’s why, and here’s what you should do instead.” That’s a real answer, not a sales tactic. We’d rather lose your project than oversell you on a build you’ll regret.
If we say no: no charge. You leave with our recommendations. If we say yes, we move to step 3.
Written proposal + timeline
If automation makes sense, we send a written quote within 1–3 business days. The quote names:
- check_circleThe exact systems we’ll build
- check_circleThe total cost (no surprises later)
- check_circleThe delivery date — the one we’re contractually on the hook for
Take your time. Run it past your business partner, your accountant, your spouse. No pressure to decide on the spot.
Kick-off — 50% up front
If you accept the proposal, we sign a contract that locks in both the start date AND the finish date. You pay 50% up front. We start building. The finish date in your contract is the one this whole guarantee hangs on.
Build, ship, test together
We build to the spec. You see progress along the way — weekly check-ins, working drafts, demo links. Nothing ships in the dark. When the system is live, tested, and meets the agreed spec, the project is done.
Scope change? If you want to add something mid-build, we send a written change order: new scope, new cost delta, new delivery date if needed. Both sides sign before we touch it.
Final payment (or not)
We earn the second half by hitting the date in your contract. The second half is your protection — earned by shipping on time. Most builds ship without ever testing the guarantee; it’s there for the rare exception. After delivery, ongoing support and hosting options are set out in your proposal — you choose what makes sense for your build.
Come with a few answers ready.
You don’t need to have it all figured out — that’s what the audit is for. But the more clarity you bring, the more useful the 20 minutes are. Think about these six before the call.
Where did your week go last week?
Scroll through your calendar or invoices to jog memory. Which 2–3 tasks ate the most time? What kept you working past 6pm?
What did you do manually that should be automatic?
Customer FAQs you answered three times? Quotes you typed from a paper pad? Review requests you forgot to send? The same email you keep writing?
What tools do you already pay for?
Jobber, ServiceTitan, Housecall Pro, Dentrix, BoldTrail, Pipedrive, HubSpot, QuickBooks, Xero, Mailchimp, Stripe, Twilio, Google Workspace — if it has an API or a webhook, we connect to it. We connect to what you already use. We don’t replace it unless we should.
Anything privacy-sensitive in your business?
Customer files, financial data, patient records, legal documents, anything covered by PIPEDA or a provincial regulator. We’ll talk through cloud vs on-premise builds.
If everything ran on autopilot, what would you do with the time?
Real answer, not “grow the business.” What specifically would you do with your Tuesday afternoon if you had it back? Sales calls? Hiring? Family? Sleep?
Rough budget if we find something worth doing?
$500–$2K? $2K–$10K? $10K–$25K+? Doesn’t lock you in — just helps us calibrate the proposal to something realistic. “I don’t know yet” is also a fine answer.
Can’t answer some of these yet? That’s normal — especially if you’ve never thought about automation before. Just bring what you have. The audit itself helps you see the rest.
Clear communication keeps the timeline on track.
The fastest builds we ship are the ones where both sides stay responsive. Here’s what that looks like in practice — on our end and on yours.
What we commit to
- scheduleEmail responses typically within 2–3 hours during business hours (Mon–Fri, 9am–5pm AT)
- mark_email_readEvery request acknowledged within 1 business day, even if the full answer takes longer
- updateWeekly check-ins with progress notes, demos, or working drafts through the build
- emergency4-hour emergency response for clients on an ongoing-support agreement
What helps us hit your date
- forumReplies on questions, approvals, or reviews within 1–2 business days — this is the single biggest thing that keeps your delivery date on track
- keySystem access by the agreed start date — logins, API keys, or whatever we need to read from. We’ll send a short checklist before kick-off so nothing’s a surprise.
- personOne point of contact at your end with authority to approve scope and sign off — avoids the “let me check with my partner” delay loop
- drawHonest feedback fast — if something we ship isn’t right, say so quickly. Bad-feedback-loops kill projects more than bugs do.
If we’re waiting on something from your end, the contract clock pauses. We’ll tell you in writing when it pauses and when it restarts. The guarantee covers delays we cause — not delays caused by waiting on your team. Fair on both sides.
50% up front. 50% when we ship on time. The second half is your protection.
Every contract has your delivery date written in. We earn the second half by shipping on that date — it’s the insurance you keep if anything slips on our end. Most builds ship without ever testing the guarantee. It’s there so you know what happens if they don’t.
Your exact timeframe is in your contract. These ranges are the typical bands — your build might come in faster or slower depending on scope. The date in your signed contract is the one we’re on the hook for. Not a marketing average.
What if?
The questions clients ask about how the process actually plays out.
What if step 2 is no?
What if I want to add scope mid-build?
What if you ship on time but I’m not happy with it?
What if my business delays the project — not yours?
Is ongoing support part of the guarantee?
What stops you from just quoting a giant timeline so you never miss?
“Aaron has been such a huge help to Lily’s Place. He’s generously volunteered countless hours that have saved us at least months of backend work. He’s also set things up so manual tasks are now automated — our Facebook posts now seamlessly share to our blog, so supporters who aren’t on social media can still get timely updates.”
Built by LogicPros — 21 years in Atlantic Canada tech · Microsoft, CompTIA, Meta certified · Service NB alumnus.
Want to see step 1 in action?
Book my free audit20 minutes. You walk us through your week. We name what’s costing you the most time.