Enquiries need chasing
Requests arrive in different places and it is hard to see who needs a reply or what happens next.
BUSINESS TOOLS & AUTOMATION
Give enquiries, quotes and job details a clearer route through your business. Start with one process that keeps getting in the way, then build the tool that fits it.
With Brodie Brittain
Sault Ste. Marie, Ontario · Projects across Canada
A GOOD STARTING POINT
A useful starting point is a repeated handoff: the moment information moves from a message into the next task.
Requests arrive in different places and it is hard to see who needs a reply or what happens next.
The same customer or job information moves between a spreadsheet, a quote and another system.
Someone has to search messages or ask around to work out the latest stage of a job.
WHAT WE COULD BUILD
These are possible parts of a project. Your quote sets out the work we agree to include.
Capture & organise
A scoped tool can bring enquiry details, status, notes and an owner into one view, with a clear way to find the next action.
Prepare & review
Quote builders, checklists and draft updates can use agreed records. We define calculations, review steps and what happens when information is missing.
Share & connect
A client portal or software connection can share selected project details. We check available integrations, access permissions and subscription requirements first.
Assist a specific task
Optional AI can help summarise enquiries, draft from job notes or find information in approved documents. We agree its sources, access and review boundaries.
A CONNECTED PROJECT
Tate Will Do It brings a contractor website and a private workspace into one project: enquiries, job files, quotes, invoices and recorded payments.
The screenshot above comes from an isolated training copy. It contains sample data, and does not expose the live workspace.
Read the Tate case study Visit the public website (opens in a new tab)THE WORK, CONNECTED
Start with the enquiry and the details of the work.
Build line items and review the figures in the job workspace.
Bring job files, invoices and recorded payments into the same project.
A payment record documents a payment; it is not a payment processor.
TRY AN IDEA
Fictional concepts with sample data. Explore the interactions before we talk about your own workflow.
HOW WE GET THERE
We map where the information comes from, who uses it and where the handoff gets difficult.
We agree access, integrations, subscription or usage costs, what can run automatically and what needs your review.
Use a working preview with sample records. Test normal work as well as missing details, duplicates and failed connections relevant to the scope.
We check the agreed workflow, hand over access and instructions, and agree how changes and support will be handled.
CLEAR BEFORE WE START
You approve the scope and price before work starts. The quote sets out the design, build, testing and handover, along with any agreed running costs.
One-hour initial minimum per new engagement, then 15-minute increments. Technical investigation starts only after you approve an estimate and spending cap.
Fixed projects start with a 50% deposit. The remaining 50% is invoiced at the agreed completion and due within 14 days. Hourly work is invoiced at completion or monthly, also due within 14 days. Additional scope, third-party costs, travel and purchases need your written approval. Hosting, AI usage and maintenance may have agreed ongoing costs; there are no automatic rush, late or renewal fees.
BEFORE WE TALK
Yes, where the software supports it. I offer IT consulting, setup and integrations for tools such as Microsoft 365, Jira, Freshservice and ManageEngine. We check the available connections, permissions and subscription requirements before agreeing the work.
No. A small tool, a software setup or an automation can be the whole project. If a website also needs to feed information into it, we can agree that connection as part of the scope.
Only if it helps with a specific task. Predictable steps may be better handled with fixed rules. We agree what can run automatically and what needs your review, especially customer messages and business decisions.
We agree which accounts and people need access, what information is used and what may be shared before the build. Start the first conversation with a made-up or anonymised example.
The scope should define how relevant failures are surfaced, what can be retried and when a person takes over. I test the agreed features with realistic examples, including what happens when something goes wrong.
YOUR NEXT STEP
Tell me what you do by hand, which tools you use, and what you wish happened next.
A first conversation is free,
up to 20 minutes.