Team hours invested
2,961
Actual time recorded across the partnership
A×S
Aruza × SRB
Centerpoint partnership value
Through July 2026
Centerpoint · Aruza’s purpose-built sales operating system
Built for Aruza’s track. Engineered for the road ahead.
Aruza is not one of thousands of customers adapting to a generic product. Centerpoint brings its sales motion into one governed platform—one place for OSPs, D2D representatives, leads, inspections, proposals, contracts, customer signup, scheduling, and management visibility.
Aruza has an ambitious goal: triple the company’s size. The platform—and the pit crew that built it—are here to help make that next level possible.
Built around AruzaEvolved with the teamConnected end to end
Hours contributed
745
Team time delivered but never billed
Major Centerpoint systems
12
Connected around Aruza’s operating model
Alignment cadence
Weekly
Long-running team check-ins and decisions
Custom, not commodity
This was not a Ford bought from a dealership that sells the same model to thousands of customers. It was engineered around Aruza’s own track.
The original mandate
One sales operation. One platform: Centerpoint.
The major initiatives were not isolated feature requests. They were a coordinated effort to replace fragmented sales execution with Centerpoint—a single, governed operating system built around how Aruza sells.
One home for outside sales
The problem
OSPs were working across multiple systems, creating fragmented records, duplicated effort, and inconsistent handoffs.
What we built
Centerpoint brought lead capture, inspections, proposals, customer signup, scheduling, and follow-up into one connected workflow.
One operating record from first contact through closed-won.
Guardrails for door-to-door
The problem
Door-to-door representatives did not have a consistent, governed process for how field sales should move.
What we built
The D2D experience added structured lead capture, territories and map areas, permissions, roles, and defined handoffs.
Field speed without sacrificing management control.
Consistent customer agreements
The problem
Contract language and sales documents varied across people and processes, creating avoidable risk and confusion.
What we built
The proposal, signup, and contract-generation flow standardized how terms are presented, approved, and recorded.
A more consistent customer experience and business process.
A connected operating ecosystem
Centerpoint is the car—but it runs across a complex network of systems.
A single sales workflow can cross Centerpoint, an external API, authentication, data mapping, webhooks, storage, communications, and the system of record. That connected power is what makes the platform valuable—and what makes experienced ownership essential.
Centerpoint at the center of the operating network
Different features use different connections; each connection has its own uptime, credentials, limits, data contracts, and failure modes.
Centerpoint
The central sales platform
One experience coordinating many specialized systems behind the scenes.
FieldRoutes
Voice for Pest
CallRail
Twilio
WiseTack
Samsara
Listen360
Google Maps
Google Drive
Google Cloud Storage
SRB shared services
An upstream system goes down
The connected workflow can stall.
A partner service can be offline, degraded, or rate-limited. Centerpoint may still load while the handoff behind a sale, call, map, report, or sync is unable to finish.
An API or credential changes
A healthy car can appear broken.
Vendors change authentication, payloads, webhooks, and limits. A previously reliable connection can fail even when Centerpoint’s own code and infrastructure are operating normally.
The pit crew responds
Trace the chain. Find the fault. Get back on the road.
The original crew understands the browser, Centerpoint API, business rules, credentials, data mappings, storage, and partner responses—so it can isolate the failure and restore the affected workflow quickly.
The engineering depth underneath those connections
202K+
Nonblank source lines
201,857 lines across tracked production application code
48
Active application routes
Workflows, dashboards, tools, and customer-facing journeys
345
Custom React components
Purpose-built interface components, excluding UI-library primitives
417
API actions
Business operations exposed across 55 API controllers
Repository measurement as of Aug. 31, 2026. The integration inventory reflects named production touchpoints in current source: FieldRoutes, Voice for Pest, CallRail, Twilio, WiseTack, Samsara, Listen360, Google Maps, Google Drive, Google Cloud Storage, and SRB shared services. Different workflows use different subsets. Source-line count includes tracked production .NET, TypeScript, React, and CSS code; it excludes blank lines, tests, dependencies, generated output, migrations, and generated client types.
Built for the next level
A custom race car deserves the pit crew that knows every bolt.
Centerpoint is the car. The original builders bring the context, care, and response capacity to keep it dependable, tuned, and evolving as Aruza grows.
Institutional memory
The original team knows why each component exists, how the systems connect, and which tradeoffs shaped the build.
Pit-lane response
Reserved capacity means the people who understand the machine can diagnose issues and respond without a long rediscovery cycle.
Continuous tuning
As branches, workflows, integrations, and customer expectations change, the system can be adjusted instead of allowed to drift.
A shared finish line
Our success is measured in what Aruza can accomplish. We win when Centerpoint helps the company scale, operate better, and reach its goals.
A general software vendor
Sees a ticket and a codebase.
It must first relearn the architecture, business rules, integrations, history, and hidden dependencies before it can safely change the system.
A dedicated pit crew
Sees the whole car and the next race.
The builders stay connected to Aruza’s team, respond with the full history in mind, and tune Centerpoint around the company’s next operating need.
What this partnership means to us
We are grateful to help build what Aruza is becoming.
Aruza is a hypergrowth company with a bold goal to triple. That makes Centerpoint more than a software build for us. Every member of the SRB team feels the weight and responsibility of helping remove friction, unlock capacity, and enable the people behind that growth.
We value this relationship deeply, and we do not take Aruza’s trust lightly.
Gratitude
Invited to build alongside an ambitious team.
Responsibility
Systems our entire staff is accountable for.
Shared ambition
Using our abilities to help unlock Aruza’s next stage.
Operating outcomes
Centerpoint is already carrying real sales volume.
It is not a concept deck—it is the system Aruza uses to track leads through closed-won outcomes. The current dashboard view shows the scale of activity moving through Centerpoint.
Closed-won outcomes
9,565
Sales marked Closed Won in Centerpoint
Tracked won value
$3.28M
Centerpoint Closed Won $
Total leads tracked
22,857
Included in the displayed dashboard view
Overall conversion
41.8%
Reported by the Lead Flow Funnel
Source: Aruza Centerpoint Branch Manager dashboard, Lead Stats view, Feb. 1–Aug. 31, 2026, filtered to Outside Sales with five displayed closed-lost exclusions. “Tracked won value” reflects the dashboard’s Closed Won $ field. These figures describe business activity tracked through Centerpoint; they do not claim the software alone generated the sales.
Invested in the relationship
We proactively gave more than the invoices required.
This was intentional, relationship-first contribution—not work Aruza was contractually owed. Hours were removed before billing, and then additional discounts were applied to the labor that remained.
Two separate layers of contribution
First we contributed time. Then we discounted the labor that reached an invoice.
Stage 1 · Before billing
745 hours
Proactively delivered at no charge
2,216 billed
745 free
25.2% of all recorded team time was contributed.
Free support
303 hrs
Other non-billed work
442 hrs
Standard-rate equivalent$186,250
Stage 2 · After billing
$41,850
Additional labor discounts
$512,400 net
7 invoice-level discounts were applied after billed hours had already been reduced.
Gross invoiced labor
$554,250
Net labor billed
$512,400
Discounted after hour reductions7 invoices
Contributed time
$186,250
Invoice discounts
$41,850
Proactive relationship contribution
$228,100
The combined figure is the standard-rate equivalent of 745 intentionally non-billed hours at $250 per hour ($186,250), plus documented discounts on invoiced labor ($41,850). It excludes hosting and service charges. Exact reconciliation remains available in the accounting appendix.
Effort by year
The build accelerated as Aruza’s operating ambition grew.
Annual cohorts now focus on the work itself: total hours delivered, the portion billed or contracted, and the portion contributed by the team.
2024
595 hours
Total team effort delivered
17.6% contributed
Billed / contracted
490 hrs
Contributed
105 hrs
2025
1,546 hours
Total team effort delivered
22.4% contributed
Billed / contracted
1200 hrs
Contributed
346 hrs
2026 YTD
820 hours
Total team effort delivered
35.9% contributed
Billed / contracted
526 hrs
Contributed
294 hrs
Billed and contributed hours by year
2026 reflects activity through July.
The pit crew in practice
The pit crew turns shared ambition into a weekly operating rhythm.
The same team that understands the machine stays connected to the people driving it. Weekly check-ins convert that context into visible priorities, decisions, ownership, and progress.
Client-supplied estimate
RFP Management System
≈100 hours
Built to make management of initiatives and team efforts more visible—creating a shared view of requests, priorities, ownership, status, and delivery.
Primary purpose
Visibility
Operating view
Shared
The 100 hours are treated as an initiative allocation within the 2,961 recorded team hours, not as additional hours.
Weekly operating cadence
Every week
Long-running team check-ins kept stakeholders on the same page as the work evolved. The cadence provided a regular forum for progress review, priority decisions, dependency resolution, feedback, and shared accountability.
What a dedicated pit crew makes possible
Aruza gets implementation capacity plus the original crew’s context, coordination, and durable management rhythm around Centerpoint.
Major systems delivered
Centerpoint, component by component.
These are not twelve separate apps. Leads, field sales, inspections, proposals, contracts, signup, scheduling, dashboards, retention, and management tooling were engineered as coordinated components of Centerpoint—Aruza’s unified sales operating system.
Built and tuned around real operations
Hours are grouped from Asana task names, tags, notes, and client context. Retention is anchored to the signed proposal; the RFP System includes the client-confirmed estimate of approximately 100 hours.
Estimated team hours by major system
| Initiative | Est. hours | Evidence |
|---|---|---|
| Lead System | 452.5 | Medium |
| D2D / Door Knocking App | 397 | High |
| Retention Wizard | 264 | High |
| Inspection System | 246 | High |
| Lead Dashboard | 137.5 | High |
| Task System | 102 | High |
| Customer Signup Wizard | 102.5 | Medium |
| RFP Management System | 100 | Medium |
| Phone System Integration | 80 | High |
| Scheduling System | 74.5 | High |
| Proposal System | 69.5 | High |
| Branch Manager Dashboard | 52.5 | High |
Finance appendix: estimated cost allocation by initiativeOpenClose
| Initiative | Est. hours | Est. attributed cost |
|---|---|---|
| Lead System | 452.5 | $72,977.26 |
| D2D / Door Knocking App | 397 | $70,751.16 |
| Retention Wizard | 264 | $58,919.52 |
| Inspection System | 246 | $37,843.65 |
| Lead Dashboard | 137.5 | $26,132.44 |
| Task System | 102 | $19,744.51 |
| Customer Signup Wizard | 102.5 | $18,389.5 |
| RFP Management System | 100 | $17,304.96 |
| Phone System Integration | 80 | $15,195.53 |
| Scheduling System | 74.5 | $13,937.3 |
| Proposal System | 69.5 | $11,227.27 |
| Branch Manager Dashboard | 52.5 | $9,001.17 |
This finance view is intentionally secondary. Cost is an attribution estimate because individual Asana tasks are not directly linked to Stripe invoice lines.
Complete delivery record
Go past the summary. Explore every task.
The Centerpoint system estimates are only one way to understand the work. This explorer exposes all 1,068 exported Asana tasks—every title, hour, assignee, tag, note, section, project, and dependency included in the source file.
Loading the complete task history…
Accounting appendix
Exact numbers, visible from the start.
The complete reconciled ledger is shown below for finance review. Every included invoice is current.
Reconciled invoice ledger
All included invoices are current.
| Billing month | Billing range | Invoice | Worked | Billed | Not billed | Gross labor | Discount | Net labor | Services/other | Grand total |
|---|---|---|---|---|---|---|---|---|---|---|
| Initial Retention | Jan 23–Feb 26, 2024 | SRB-1186 / SRB-1200 | 230.5 | 169 | +61.5 | $42,500 | — | $42,500 | $9,934.8 | $52,434.8 |
| May 2024 | May 1–May 31 | SRB-1220coverage gap | 0 | 38 | -38 | $9,500 | — | $9,500 | $0 | $9,500 |
| Jul 2024 | Jul 1–Jul 31 | SRB-1239coverage gap | 18 | 38 | -20 | $9,500 | — | $9,500 | $0 | $9,500 |
| Aug 2024 | Aug 1–Aug 31 | SRB-1253 | 63.5 | 30 | +33.5 | $7,500 | — | $7,500 | $150 | $7,650 |
| Sep 2024 | Sep 1–Sep 30 | SRB-1255 | 89.5 | 69 | +20.5 | $17,250 | — | $17,250 | $150 | $17,400 |
| Oct 2024 | Oct 1–Oct 31 | SRB-1263 | 119 | 45 | +74 | $11,250 | — | $11,250 | $150 | $11,400 |
| Nov 2024 | Nov 1–Nov 30 | SRB-1273coverage gap | 15 | 50 | -35 | $12,500 | — | $12,500 | $150 | $12,650 |
| Dec 2024 | Dec 1–Jan 6 | SRB-1280 | 59.5 | 51 | +8.5 | $12,750 | — | $12,750 | $150 | $12,900 |
| Jan 2025 | Jan 7–Jan 31 | SRB-1290 | 119.5 | 71 | +48.5 | $17,750 | — | $17,750 | $150 | $17,900 |
| Feb 2025 | Feb 1–Feb 28 | SRB-1296 | 59 | 49 | +10 | $12,250 | — | $12,250 | $150 | $12,400 |
| Mar 2025 | Mar 1–Mar 31 | SRB-1306 | 74 | 67 | +7 | $16,750 | — | $16,750 | $150 | $16,900 |
| Apr 2025 | Apr 1–Apr 30 | SRB-1309 | 95 | 85 | +10 | $21,250 | — | $21,250 | $150 | $21,400 |
| May 2025 | May 1–May 31 | SRB-1315 | 161.5 | 98 | +63.5 | $24,500 | — | $24,500 | $150 | $24,650 |
| Jun 2025 | Jun 1–Jun 30 | SRB-1319 | 119.5 | 87 | +32.5 | $21,750 | — | $21,750 | $150 | $21,900 |
| Jul 2025 | Jul 1–Jul 31 | SRB-1322 | 136.5 | 87 | +49.5 | $21,750 | — | $21,750 | $837.56 | $22,587.56 |
| Aug 2025 | Aug 1–Sep 2 | SRB-1327 | 115.5 | 91 | +24.5 | $22,750 | — | $22,750 | $841.25 | $23,591.25 |
| Sep 2025 | Sep 3–Oct 6 | SRB-1332 | 150 | 145 | +5 | $36,250 | −$7,250 | $29,000 | $772.26 | $29,772.26 |
| Oct 2025 | Oct 7–Nov 4 | SRB-1336 | 144.5 | 125 | +19.5 | $31,250 | −$6,250 | $25,000 | $772.26 | $25,772.26 |
| Nov 2025 | Nov 5–Dec 2 | SRB-1340 | 94 | 73 | +21 | $18,250 | — | $18,250 | $667.92 | $18,917.92 |
| Dec 2025 | Dec 3–Jan 5 | SRB-1344 | 277 | 222 | +55 | $55,500 | −$11,100 | $44,400 | $667.92 | $45,067.92 |
| Jan 2026 | Jan 6–Feb 2 | SRB-1347 | 105.5 | 84 | +21.5 | $21,000 | — | $21,000 | $667.92 | $21,667.92 |
| Feb 2026 | Feb 3–Mar 2 | SRB-1352 | 143 | 90 | +53 | $22,500 | −$4,500 | $18,000 | $594.81 | $18,594.81 |
| Mar 2026 | Mar 3–Apr 2 | SRB-1356 | 144.5 | 85.5 | +59 | $21,375 | −$4,275 | $17,100 | $662.3 | $17,762.3 |
| Apr 2026 | Apr 3–May 4 | SRB-1359 | 156 | 84.5 | +71.5 | $21,125 | −$4,225 | $16,900 | $1,082.52 | $17,982.52 |
| May 2026 | May 5–Jun 1 | SRB-1363 | 128.5 | 85 | +43.5 | $21,250 | −$4,250 | $17,000 | $1,682.26 | $18,682.26 |
| Jun 2026 | Jun 2–Jul 1 | SRB-1366 | 102 | 66.5 | +35.5 | $16,625 | — | $16,625 | $2,427.58 | $19,052.58 |
| Jul 2026 | Jul 2–Aug 3 | SRB-1370 | 40.5 | 30.5 | +10 | $7,625 | — | $7,625 | $1,236.13 | $8,861.13 |
| All current invoices | 2,961 | 2,216 | +745 | $554,250 | −$41,850 | $512,400 | $24,497.49 | $536,897.49 | ||
All included invoices are current. Reconciled invoice total: $536,897.49.
Three older ranges have incomplete task coverage in the current Asana export and are flagged above.