Skip to Main Content
D-Tools Cloud Ideas Portal

We actually read these.

Ideas submitted here go to the product team, not into a void. Add yours, vote on others, and comment on what matters to your business.

Talk to our Product Managers live: every other Monday, 1:00–2:00 PM ET → https://www.d-tools.com/cloud-product-office-hours

Created by Dave Kirn
Created on May 10, 2026

Org Scaling: Specialized roles beyond the two-person sales-consultant + project-manager model

The current platform is structured as a two-person operating model: a sales consultant runs the sales motion, a project manager runs delivery, and everyone else gets bolted on with admin-level permissions because the system doesn't have the role granularity to support a real org chart. This works at 5-10 people. It breaks at 20-30+.

Examples of roles that don't have first-class support today:

  • Dispatcher — schedules service techs but doesn't manage projects or write proposals.
  • AR clerk — handles invoicing and collections but doesn't see project margins or technician costs.
  • Procurement / purchaser — orders parts but doesn't approve budgets or sign change orders.
  • Field supervisor — signs off on tech work but doesn't manage the full project.
  • Inside sales / quote builder — drafts proposals but doesn't own the customer relationship.
  • Operations manager — oversees scheduling, dispatch, and quality but isn't a PM or owner.

Each role needs scoped permissions, a focused UI experience, and the ability to do their job without seeing everyone else's data or having admin rights they don't need.

What does your team's org chart look like today, and which roles aren't well-served by the current platform? Drop a comment with your specific scenario — the more concrete examples we collect, the better we can shape this into something that fits how shops actually scale.

  • Attach files