Free 20-minute consultation ↗OpSmith is based in Winnipeg and works directly with established local businesses that want to reduce recurring administrative work without losing the operating knowledge of the people who currently keep it moving.
Work directly with Terry Williams, founder of OpSmith, from understanding the process through design, testing and launch. Based in Winnipeg, Terry can observe local handoffs on site when that makes the workflow clearer.
For a building-material supplier, Terry built an AI-assisted house-wrap visualizer connected to instant quoting and automated follow-up. Customer selections became the input for the next step instead of being recreated by a salesperson.
The case study describes 3–4 hours of repeated preparation removed per prospect sequence—not time removed from the final sales conversation. The system took several months of design, implementation, testing and refinement.
Custom visualizer and quote automation case study
For Winnipeg teams, Terry can examine the process where it happens—inside the real combination of people, software, documents and workarounds that a generic remote demo may miss.
OpSmith serves Winnipeg businesses that have real process volume, disconnected information and a team that has outgrown informal workarounds.
Meet the people involved, follow the request or document through its actual path and record the waiting, re-entry and exceptions.
Choose the smallest system that reduces friction while preserving the approvals, customer judgment and recovery paths the business needs.
Test the workflow with representative inputs, document ownership and remain available as the local process or operating rules change.
These are illustrative workflow designs, not claims about local client results. Each starts with your existing tools and a baseline your team can check.
Not sure which process is worth changing? Use the automation ROI calculator to compare cash savings, staff capacity and payback after implementation costs and human review. Test conservative and expected scenarios; the results are planning estimates, not a project quote or promised saving.
Start with one operating problem. An initial conversation does not commit you to a build, and an assessment may recommend process cleanup or leaving a step human.
For teams in construction or property management, the assessment follows the actual field-to-office handoffs. Remote work can support later design and delivery; an on-site visit is useful when observing the process will change the recommendation.
Strong starting points include quoting and customer intake, construction-office administration, property-management requests, logistics documents, reporting and processes unique to the way a local business competes.
The first 20-minute consultation is free. A paid Blueprint and any implementation are scoped separately. Cost depends on the number of systems and handoffs, data cleanup, business rules, human review, testing and ongoing support. Discuss software and usage charges as well as the build; a process-cost estimate is not a project quote.
Timing depends on scope, access to existing systems, source-data quality, exception handling and how quickly the team can test and approve changes. A bounded handoff and a bespoke customer journey are different projects. We establish the scope and dependencies before proposing a delivery schedule, rather than promise the same turnaround for every business.
Start with a process owner, a description of the current steps and non-sensitive representative examples. During an agreed engagement, access to systems, business rules and feedback from the people doing the work are needed to design and test the workflow. Do not send credentials or confidential records through the public contact form or chat.
Yes, when seeing the physical handoffs, documents or team interactions will materially improve the workflow assessment. Later design and support can continue remotely when that is more efficient.
No. OpSmith is based in Winnipeg and serves Canadian businesses remotely, with the option for in-person workflow observation for local teams.
The strongest fit is an established organization with recurring operational volume, disconnected systems or a process that has become too dependent on manual coordination.
No. Begin with the operating problem. The recommended system may use rules, integrations, conventional automation, AI assistance or a combination based on the work and its risks.
Explore office and field handoffs common to Winnipeg contractors and trade businesses.
Improve maintenance, tenant, vendor and reporting workflows.
Map one local operating bottleneck before deciding what to build.
Use OpSmith’s workflow automation resources and guides to document the work, control exceptions and measure the operating change.
Score repetition, data, exceptions, risk and business value before selecting a build.
Document triggers, inputs, decisions, approvals and handoffs.
Test whether the workflow is stable and understood enough to automate.
Tell us how the process works today, where it slows down and what a better handoff would change. We will use that context in the first conversation.