The Situation
Dapt’s CEO originally brought Sarah in for marketing — building LinkedIn reach, SEO, and an affiliate program to get ADP solution providers selling Dapt alongside their own services. That work meant getting close to how the business actually ran.
What surfaced was a company with no real operational backbone. The CEO kept several spreadsheets he filled in when he remembered to. There were multiple CRMs, each half set up, none talking to each other. The engineering team ran entirely out of Jira, disconnected from everything else. Stripe was processing real monthly revenue with no link to any other system. Nobody — not sales, not support, not the CEO — had a reliable way to see what was actually happening in the business.
What was built
A full-funnel operating system in Monday.com — connecting sales, onboarding, and customer service into one pipeline, bridged live to the engineering team’s Jira instance so nobody had to change how they worked.
- A full-funnel CRM in Monday.com — leads, deals, and sales communication tracked in one board, handing off cleanly to onboarding the moment a deal closes.
- Onboarding and customer service boards — onboarding project-managed each new client through setup; customer service got its first real SLA tracking and issue visibility.
- A live Monday–Jira bridge — custom Cloudflare Workers and webhook automations moving information both directions, plus new automations on the Jira side so engineering’s own workflow moved faster too.
- Team dashboards — the first high-level view any team at Dapt had of their own metrics.
- Ongoing maintenance and a mid-course rebuild — kept the system running through a Jira platform update that broke the bridge, and later scoped the move to a Jira-centered structure when leadership decided to consolidate.
What the user does each week:
- Open the file
- Paste 16–17 rows of provider data into the blue zone
- Set the date and pick “Trial” from the dropdown
- Press Ctrl+Alt+F9
One client, one record, one system — from first contact through renewal, without engineering ever having to leave Jira.
How It Was Done
The first month went to a systems audit: pulling data out of every spreadsheet and half-built CRM Dapt had been using, cleaning and deduping it, and laying out the pros and cons of the platforms that could serve as the company’s operational hub, weighed on cost against what Dapt actually needed at its stage. Monday.com won — it was the least expensive option that could do the job, and because it’s database-based under the hood, structuring the data cleanly there meant Dapt could migrate to something more robust later without starting over. Jira stayed in place for engineering, since it was already working for them.
From there, three months went to building the full-funnel CRM, the onboarding and customer service boards, and the connective tissue between them and Jira — custom Cloudflare Workers and Monday.com webhook automations moving records and updates both directions in real time. Jira itself hadn’t been set up to use much of its own automation, so part of the build included new Jira-side automations to move engineering’s work through their process faster.
The system ran and was actively maintained for months afterward. When a Jira platform update over New Year’s broke the bridge without warning, it was rebuilt against Jira’s new setup within days, so no team lost visibility mid-stream. When Dapt later decided to consolidate everything into Jira, the same systems thinking carried into researching and scoping the Jira-based structure to replace it.
The Outcome
For the first time, Dapt could see a customer’s full lifecycle in one place — sales, onboarding, and support all speaking to each other, with engineering still working exactly the way they preferred. Each team got a dashboard showing metrics they’d genuinely never had visibility into before.
The before-and-after was night and day. I went from 'I think things are going okay' to being able to clearly show our SLAs being met and exceeded, with the data to prove it. She gets a messy operations stack, fixes it without breaking the people doing the work, and stays long enough to make sure the new system actually holds.
What isn’t in the pull-quote above is worth telling too: this teammate was newer to systems work and working from a different continent than the rest of Dapt’s team, which meant a lot got lost in translation — both in how the systems were designed and in how decisions got made. Beyond the build itself, that became a mentoring relationship: walking through the why behind the setup, not just the how, so the skills would carry into whatever came next. Long after the active engagement wound down, the check-ins have continued.
What Made this project work
- Trust built during the earlier marketing engagement meant leadership brought this in the moment the operational gap became impossible to ignore — it didn’t require a separate sales process.
- The platform decision was made on cost and fit for Dapt’s actual stage, not familiarity or hype — and structured so a future migration wouldn’t mean starting from zero.
- The engineering team’s workflow was never touched. The system was built to bridge into Jira, not force everyone out of it.
Most growing companies don’t need to rip out the tools their team already trusts — they need someone to connect them, clean the data underneath, and stay long enough to make sure it holds.