Case Study · Healthcare · B2B SaaS · AR/RCM
AR Proactive deploys new features 80% faster — and boosts revenue with Sphere.
AR Proactive — a B2B SaaS for healthcare accounts receivable and revenue cycle management — needed to ship faster, onboard customers faster, and align dev with product. Sphere embedded a senior delivery pod, rebuilt CI/CD, and rewrote the operational machinery underneath.
- Built by
- Sphere Delivery Pods
- Industry
- Healthcare · AR / RCM SaaS
- Published
- June 11, 2026
- Reading time
- 10 minutes
- Status
- Delivered · engagement ongoing
If you only read one box.
AR Proactive had a working product. What they didn’t have was the cadence to ship fast enough to win new customers and keep current ones expanding. Sphere brought a senior pod and the machinery underneath it: CI/CD, prioritization, and a written communication strategy that kept dev and product moving in the same direction.
The fix was operational, not technical-only. CI/CD landed inside the development environment so deploys went out automatically. Jira moved from a backlog dump to a planning system. The team adopted a written communication discipline that kept engineers and leaders on the same page.
The result, delivered: 80% reduction in feature deploy time (the year-one target was 50%), 4 new customers onboarded during the engagement, and a 10%+ revenue lift. The follow-on project is already underway.
The situation
A customer raises a workflow tweak through support. It’s the kind of change that should ship in days.
Before Sphere
Ticket creation → completion stretches across weeks. Releases batch up; the team can’t answer "when?" with confidence.
With Sphere’s Pod
With a managed prioritization process and CI/CD wired into the dev environment, the tweak ships in the next deploy window. Customer hears "shipped" before the week ends.
The situation
A prospect wants a custom workflow configured during onboarding.
Before Sphere
Onboarding takes weeks. Configuration sits in a queue behind release work.
With Sphere’s Pod
Faster delivery cadence + the new design system let the team onboard 4 new customers during the engagement — contributing the 10%+ revenue lift.
The situation
The product team and engineering disagree on what ships next.
Before Sphere
Roadmap drift. Each sprint, a different priority wins. No shared communication ritual.
With Sphere’s Pod
Sphere brought in a Project Manager + a written communication strategy between developers and leadership. Roadmap commitments stick; sprints close on time.
Chapter 01
The bottleneck wasn’t the product — it was the cadence.
In plain English
AR Proactive had a working B2B SaaS for healthcare revenue-cycle management. What they didn’t have was the operational machinery to ship new features fast enough to win and onboard customers.
AR Proactive simplifies the workflows around AR (accounts receivable) and RCM (revenue cycle management) for healthcare organizations. The product was solid; the constraint was throughput. New feature deploys were slow, the ticket-to-completion window was wide, and onboarding a new customer with custom workflows took weeks the team didn’t have.
When they came to Sphere, the brief was direct: cut deploy time by 50% inside the first year, shorten the time from ticket creation to completion, shrink the "time to wow" for new customers, and align dev with product. The goal underneath all of it: speed up business value delivery so the platform could onboard new accounts and keep current ones expanding.
The work split into two streams: an embedded delivery pod (PM, developers, DevOps, QA, designers — the people doing the work) and an operational layer (process, prioritization, communication — the rails the work runs on).
Chapter 02
CI/CD first. Process second. Tools third.
In plain English
Speed gains came from three places, in that order: an automated deploy pipeline, a managed prioritization process, and the right tools given to senior people who already knew how to use them.
The first technical lift was building CI/CD into the development infrastructure. Before Sphere, releases were manual and batched. After, deploys ran through an automated pipeline with tests, environments, and rollback. The headline outcome: an 80% reduction in feature-deploy time — well past the 50% target the client set for year one.
In parallel, the team cleaned up the database and tuned the loading performance of the web-based tool. CI/CD work continued through weekends and holidays where it had to, so end users were never without coverage. The bar was simple: deploys go out smoothly, no production bugs slip through.
On the process side, Sphere rebuilt prioritization with the client’s customers in the loop. Jira moved from a list of work to a system you could plan in. Project Management best practices created a written communication strategy between developers and leadership — so the team always knew what was next, and leadership always knew where things stood.
Chapter 03
What an extension team looks like, when it works.
In plain English
Numbers below are delivered outcomes from the engagement — measured deploy speedups, customer adds, revenue movement — not modeled estimates.
Delivered outcomes during the AR Proactive engagement.
| Metric | Before Sphere | Delivered | Delta |
|---|---|---|---|
| Feature-deploy time reduction | Manual · batched | CI/CD · automated | −80% (vs 50% target) |
| New customers onboarded during engagement | — | 4 | +4 |
| Revenue lift | — | +10%+ | +10%+ |
| Extension-team growth | — | 5+ devs, DevOps, designers | +5 senior hires |
| Bugs introduced post CI/CD rollout | — | 0 | Clean rollout |
| Dev ↔ Product alignment | Ad-hoc | Written cadence + PM-owned | Established |
Numbers are measured outcomes from the engagement, not modeled estimates.
Calculate your team’s deploy-overhead cost
Enter your team to see how much engineering capacity slow deploys are burning.
Sphere builds this for you with a senior pod.
Sphere’s Delivery Pods bring PM, developers, DevOps, QA, and designers — people who already know the playbook — directly into your engineering org. We own the rails (CI/CD, Jira, prioritization, communication cadence) while your team owns the roadmap.
Get a delivery pod plan for your engineering team.
Sphere will scope the pod composition (PM, devs, DevOps, QA, design) and the operational rebuild (CI/CD, Jira, prioritization) for your team — at no cost.
Chapter 04
The secondary effect we didn’t design for: confidence.
In plain English
Three quotes from AR Proactive leadership, sent unprompted during the engagement. Two are about weekend work. One is about a feature ship that closed expansion revenue.
When a client takes the time to write — by name, to a specific engineer — after a weekend push, it tells you the partnership has moved past vendor mode. AR Proactive’s notes (preserved verbatim in the testimonials section below) name Konstantin, Rifat Ul Alom, and Arslan. Two are about availability through weekends and holidays to keep the platform fast and stable. One is about a single feature release — a color palette update on the Bucket Notes workflow — that gave a current customer (Symphony) the confidence to sign two of their child companies onto Workflows.
That last note matters operationally. The thing that drove expansion revenue wasn’t a redesign or a re-platform. It was one feature, shipped with confidence, on a cadence the customer could rely on. The CI/CD work and the process changes are what made shipping that feature unremarkable instead of heroic.
Unprompted, mid-engagement
What AR Proactive’s team said, by name.
Weekend push to improve site speed and stability.
“Hi Konstantin, just wanted to send you a quick message to say thank you for taking the time to work over the weekend. I appreciate your extra hours and putting in the time to make sure the site’s working fast, robust, and stable. Keep it up. I appreciate working with you and let’s see how fast and how smart we can make the product. Let’s keep on building. Thank you.”
Color-palette release on Bucket Notes — drove customer expansion.
“I want to say a big Thank You to Rifat Ul Alom (Developer) and Rodrigo Ferrari (PM) on the Workflows Team. They released the new color palette on Bucket Notes. This feature release gave the confidence to our current customer Symphony to sign up 2 more of their child companies to Workflows. Well done on adding business value to our customers, to help them solve their problems!”
Weekend server work — speed and performance hardening.
“Hi Arslan, just wanted to say thank you for working on the weekend and improving our servers and checking speed and performance. I appreciate you taking the extra time. Thanks to your family as well for letting you do that and I appreciate your hard work. You’re a pleasure to work with. So keep on pushing the boundaries.”
Chapter 05
What ships, what holds. We are transparent about both.
In plain English
The engagement is active and outcomes above are measured, not modeled. Sphere is currently running a follow-on project with AR Proactive driven by the success of the first one.
What Sphere shipped
- CI/CD pipeline built into the development infrastructure — automated deploys, tests, environments, rollback.
- Managed prioritization with customer-in-the-loop input, replacing ad-hoc roadmap drift.
- Jira reorganized as a planning system, not a backlog dump.
- Database cleanup + load-time tuning on the web-based tool.
- Project Management cadence with a written communication strategy between developers and leadership.
- Design system refresh — new screens for a better user experience during onboarding.
- Extension team in place — PM, developers, DevOps, QA engineers, designers — all senior.
- Weekend / holiday coverage during critical rollouts so end users were never unsupported.
Engagement context
- Engagement still active — Sphere is now leading a follow-on project with the same client.
- B2B SaaS for healthcare AR/RCM — Sphere extension team integrated into the in-house engineering org.
- CI/CD rollout had zero production bugs identified post-deploy.
- 4 new customers onboarded within the engagement; 10%+ revenue lift attributed.
- Customer-expansion impact (Symphony → 2 child companies) attributed to a single feature release on Bucket Notes.
- Year-one deploy-time target set at 50% reduction; delivered 80%.
Frequently asked questions
Related from Sphere
GenAI · Influencer Marketing
Sweet Influencers — Gen-AI Platform for Franchising
An end-to-end Gen-AI POC: hybrid search, LLM brand-fit summaries, and an 11-state Campaign Cockpit.
GenAI · Workforce
AI Retail Break Scheduling — California Retailer
Modeled outcomes: 85% reduction in California Labor Code §512 violations across a 25-store deployment.
Ready to ship at a cadence your customers can rely on?
Sphere will scope the pod, the CI/CD rebuild, and the prioritization process for your engineering team — in 30 minutes.
96% client retention rate · Clutch Top AI Company, US 2025 · 148 case studies delivered