Your Durham CRO runs a study across five sites in Asana, and the protocol milestones don't fit a Kanban board
Custom project management software for a Durham research or clinical operation typically runs $60,000 to $130,000 over 4 to 7 months, though most teams should adapt Asana or Jira first. The break point is the protocol-driven study: when a 'project' is a research protocol with regulatory gates, multi-site coordination, and milestones tied to IRB approvals and data locks, a generic task board can't model the dependencies that actually govern the work.
Asana, Monday, Jira, and ClickUp model tasks, assignees, and due dates, and for normal project work that's plenty. A Durham CRO or research team runs something a task board can't represent: a study protocol with regulatory gates that must clear before the next phase, enrollment milestones across five sites, data locks, and amendments that ripple through the whole timeline. A milestone isn't 'task done', it's 'IRB approved and enrollment target met.'
So the team forces protocol logic into a Kanban board, the dependencies live in a project manager's head, and when an amendment shifts a regulatory gate, nothing updates automatically. The PM tool tracks tasks but not the protocol-driven reality, so the real project plan ends up in a spreadsheet beside it.
- Projects are protocols with regulatory gates, not task lists
- You coordinate milestones across multiple study sites
- Amendments must ripple through the timeline automatically
- The real plan lives in a spreadsheet beside the PM tool
- Your projects are normal task-and-deadline work
- Asana, Jira, or Monday models your workflow fine
- You don't have regulatory gates or multi-site coordination
- A shadow spreadsheet isn't actually necessary
- Protocol phases gated by regulatory approvals, enforced by the system
- Multi-site enrollment milestones coordinated in one place
- Amendments that ripple through the timeline automatically
- One source of truth instead of a PM tool plus a shadow spreadsheet
- Dependencies encoded in software, not held in someone's head
- Costs far more than an Asana or Jira subscription
- Adoption requires changing how the team plans and tracks
- You own the tool and its integrations as protocols evolve
- For normal project work, generic PM tools are the right answer
The honest cost picture for Durham
| Project scope | Typical cost | Timeline |
|---|---|---|
| Protocol-aware PM module with regulatory gates | $60k to $100k | 4 to 6 months |
| Full study-management platform with multi-site coordination | $100k to $170k | 6 to 9 months |
| Integration with study and document systems | $25k to $45k | 1 to 2 months |
Feature priorities for Durham teams
Durham project management: the full scope
The engagements Durham teams bring us most often: resource scheduling, Asana alternative, Monday.com alternative, Jira integration, time tracking, team collaboration software and workflow management.
Exactly what you get
Project management that models a study, not a task list: protocol phases gated by regulatory approvals, multi-site enrollment milestones coordinated in one view, data locks, and amendments that recalculate the whole timeline automatically. The dependencies live in the system, so the shadow spreadsheet disappears. It connects to your CRM for sponsor relationships, helpdesk software for site support, custom software study systems, and business intelligence dashboards for progress.
How to choose a developer in Durham
Ask a candidate to explain how a regulatory gate differs from a normal task dependency, and how an amendment should ripple through a study timeline. A Durham partner who serves CROs and research teams will answer in protocol terms; a generic PM-tool builder will reach for a Kanban board. The right partner first checks whether configuring Jira or Asana would do, and recommends custom only when protocol logic genuinely can't fit a task board.
Timeline: what happens, and when
- !A vendor who'd model a protocol as a Kanban board, ask how regulatory gates work
- !No multi-site coordination experience, ask for a comparable study build
- !No amendment-handling concept, ask how a timeline recalculates
- !They skip discovery into your protocol lifecycle, ask what their estimate is based on
- !No study-system integration experience, ask for an example
If project management is on the roadmap, field service management, booking & scheduling, mobile app usually follow within the year. Budget them as one conversation.
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Why can't Asana run a clinical study?
Asana models tasks, assignees, and dates, but not protocol phases gated by regulatory approvals, multi-site enrollment, or amendments that shift the whole timeline. For a Durham CRO, those gated dependencies are the project, which is why protocol logic ends up in a spreadsheet beside Asana.
What is a regulatory gate in PM terms?
It's a dependency that blocks downstream work until a condition, IRB approval, enrollment target, data lock, is met. Unlike a normal task dependency, it's tied to regulatory or protocol milestones, and a custom system enforces it rather than relying on a PM to remember.
Should we configure Jira instead?
Possibly, start there. For some research teams, Jira or Asana configuration handles enough. Go custom only when protocol gates, multi-site coordination, and amendment ripple effects genuinely exceed what configuration can express, which is a real but specific threshold.
How do amendments work?
When a protocol amendment shifts a milestone or gate, the system recalculates dependent dates and flags affected work across all sites automatically. That replaces the manual rework of updating a spreadsheet plan every time the protocol changes, which is error-prone and slow.