Internal tools & operations
Replace disconnected spreadsheets and manual handoffs with tools built around how your team actually works. Bring intake, review, approvals, and reporting into a shared workflow.
Software product studio · Toronto, Canada
Enterprise software built around your operations.
Based in Toronto, Canada, CMD brings product strategy, design, and software development together to turn complex workflows into useful software.
Discuss your platform →Built around the work
When your tools no longer fit your operations.
An enterprise platform should help people complete work, understand its status, and make the next decision. We work with teams whose processes cross departments, documents, and disconnected systems, and with product teams that need a hands-on delivery partner.
Connected platforms
Connect the systems you already depend on. Define where data belongs, how it moves between tools, and what should happen when an integration fails.
AI-enabled workflows
Bring generative AI into specific tasks such as reviewing documents or extracting information. Design around source evidence, human review, and clear boundaries for automated actions.
From discovery to production.
Discover the constraint
Work with operators and decision-makers to map the workflow, existing systems, users, and failure points. Define a useful outcome and the smallest release that can test it.
Design the first release
Map the user experience, data model, permissions, and integrations. Make scope and tradeoffs explicit before committing to a build.
Build with users
Put working software in front of the people who will use it. Test core workflows and integration behavior, gather feedback, and iterate against the agreed outcome.
Deploy and hand over
Plan rollout, documentation, ownership, and support with your team. Agree on what happens after launch and which signals will guide the next iteration.
Selected client work01 — 03
Tracker Networks engagement
From the first build.
To the next chapter.
Product leadership, software engineering, design, and website delivery across a continuing client relationship.
Our founder began as an independent contractor with Tracker Networks and continued the engagement through CMD.
Product engineering01 / 03
Ventrack
Built from the ground up.
CMD’s founder built Ventrack from scratch during his engagement with Tracker Networks.
Explore VentrackProduct direction & design02 / 03
Essential ERM
Direction meets detail.
Serving as Product Director at Tracker Networks, our founder contributed to the design of Essential ERM, bringing product leadership and hands-on design to the engagement.
Visit Tracker NetworksWebsite delivery03 / 03
Tracker Networks
The product’s front door.
Our work with Tracker Networks also included delivery of the company website, alongside the ongoing product engagement.
Explore the websiteCMD-owned product · In development
PlanPort
A focused example of how we approach complex work: building permit pre-review with traceable evidence.
PlanPort brings drawings, forms, reports, and municipal guidance together to check configured requirements and turn issues into findings and next actions. The product emphasizes evidence that a person can inspect and verify.
PlanPort is a CMD venture in active development. It illustrates our product approach; it is not a client delivery or a claim of measured customer results.
Explore the PlanPort product walkthrough →
Planning your platform
Can you work with our existing systems?
We start by understanding the tools, APIs, data access, and constraints already in place. That discovery determines whether to integrate, extend, or replace a particular part of the workflow.
How do you approach permissions and sensitive data?
We map user roles and data access as part of system design. Authentication, audit needs, hosting constraints, and review requirements belong in the scope before implementation; specific obligations depend on your organization and project.
What does an engagement cost and how long does it take?
Scope depends on the workflow, integration complexity, data readiness, and rollout requirements. Share the problem and existing systems so we can define a first release and discuss a realistic budget and schedule.
Who owns the software, and what happens after launch?
Ownership, confidential information, reusable studio capabilities, and ongoing support are agreed at the start of an engagement. Client work remains distinct from CMD-owned products.
Is CMD based in Toronto?
Yes. CMD is a software product studio based in Toronto, Ontario, Canada. Share where your team operates and we can discuss collaboration and delivery needs.
Start with the workflow.
Tell us where the work gets stuck, which systems are involved, and what a useful outcome looks like.
Discuss your platform →