Nexus Technologies Inc. Company Profile

Ali Süleyman Topuz

Internal Reference Document for “Transforming with AI”

Overview

Nexus Technologies Inc. is a fictional B2B SaaS company used as a running example throughout this book. Every concept, framework, and recommendation in the book is demonstrated through Nexus’s journey from zero AI capability to a fully AI-native operation.

Nexus is deliberately designed to be representative, not exceptional. It is not a Silicon Valley unicorn with unlimited engineering resources. It is not a decade-old enterprise drowning in legacy systems. It is the kind of company that thousands of technology leaders run today: well-built, growing, and standing at the threshold of a transformation it knows it needs but isn’t sure how to execute.

Company Snapshot

Product

Nexus builds a workflow and operations management platform for field service companies businesses that dispatch technicians, manage work orders, track assets in the field, and coordinate service delivery across distributed teams. Their customers include HVAC companies, facility management firms, telecoms infrastructure teams, and property maintenance organizations.

The platform covers: - Work order creation, assignment, and tracking - Technician scheduling and dispatch - Customer communication and notification - Field reporting and documentation - Billing and invoicing integration - Basic analytics and dashboards

Nexus charges $249–$699 per month per customer depending on team size and feature tier. The product is well-regarded NPS sits at 42 but customers increasingly mention that competing platforms are offering AI-powered features Nexus doesn’t have.

Team Structure

Total: 87 employees

Engineering breakdown (38 people): - Squad Alpha (Core Platform): 12 engineers - Squad Beta (Mobile & Field): 10 engineers - Squad Gamma (Integrations & APIs): 8 engineers - DevOps & Infrastructure: 4 engineers - QA: 4 engineers

No dedicated data team. No ML engineers. One senior engineer (Thomas) has experimented with OpenAI APIs in personal projects but has never used them in production.

Current Technology Stack

The architecture is solid but conservative. The team made a deliberate choice to stay with a modular monolith rather than microservices, which has served them well for reliability. However, this creates some constraints when thinking about AI workloads that may require different scaling characteristics.

Data lives in PostgreSQL four years of operational data including work orders, technician records, customer interactions, scheduling history, and billing data. The data is normalized and relatively clean for the core entities, but there is no data warehouse, no vector database, and no embedding infrastructure.

Key Pain Points

1. Customer Success Is Drowning

With 280 customers and 12 CS staff, each person manages 23+ accounts. Industry benchmark for healthy SaaS CS is 10–15 accounts per rep. Priya’s team spends 60% of their time answering repetitive questions that could be automated. Average response time is 2.8 days. Churn analysis reveals that 40% of churned customers cited “slow support” as a factor.

2. Onboarding Takes Too Long

New customers take 4–6 weeks to go live. Much of this is manual: configuration guidance, data migration assistance, training sessions. The CS team runs the same 8-step onboarding checklist for every new customer. There is no intelligence in the process a small 10-person HVAC company gets the same onboarding as a 200-person facility management firm.

3. Analytics Is Manual and Slow

Customers want insights from their operational data. Currently, Nexus’s analytics tab shows basic charts. Any custom report requires a CS rep to export data to Excel and manually build it. This takes hours per request and is not scalable.

4. Competitive Pressure

Three of Nexus’s five main competitors have announced or shipped AI features in the past 12 months: smart scheduling optimization, predictive maintenance alerts, automated customer communications. Nexus has nothing comparable. Sales is losing deals on this point David’s team logged 14 lost deals in Q3 where the prospect cited AI capabilities as the deciding factor.

5. Pricing Intelligence Gap

The sales team prices deals manually, relying on gut feel and basic tier rules. There is no model to suggest optimal pricing based on company size, usage patterns, or likelihood to expand. Discounting is inconsistent.

Business Goals for the Next 36 Months

1. Reduce annual churn from 12% to below 8%
2. Reduce average customer onboarding time from 5 weeks to under 2 weeks
3. Reduce CS ticket volume per customer by 40% through self-service
4. Win back AI feature parity with top 3 competitors within 12 months
5. Grow ARR from $9.5M to $22M by end of Year 3
6. Raise Series C at a healthy multiple AI capability is a valuation driver

What Nexus Is Not Ready For (Yet)

• A team of ML engineers: they don’t have any, and hiring is expensive and slow
• A complete infrastructure rebuild: the monolith works and the team knows it well
• Big-bang AI transformation: culture, budget, and risk tolerance don’t support it
• Replacing human judgment entirely: customers trust the platform because people are in the loop

What Nexus is ready for: a deliberate, phased, practitioner-led AI transformation that starts with what they have, builds on their existing data and infrastructure, and delivers measurable value at every step.

That journey is what this book is about.

A Note on Using Nexus

Throughout each chapter, you will find “Nexus in Focus” sections that show exactly how the concepts in that chapter apply to Nexus’s situation. These sections are designed to make abstract frameworks concrete. You don’t need to work in field service software for them to be useful the patterns Nexus follows apply equally to e-commerce platforms, HR software, logistics tools, financial services applications, and beyond.

If your organization buys rather than builds software, look for “If You’re Buying, Not Building” callouts that translate each concept into the language of procurement, vendor evaluation, and change management.