1.10: Welcome to C-Bay Inc.

Inside the Software Development Division

You’ve just joined C-Bay Inc., a fast-growing technology company headquartered in Sunnyvale, California. C-Bay specializes in integrated business solutions for small and mid-sized enterprises—combining hardware, software, cloud-based services, and ongoing client support. It serves industries ranging from healthcare to logistics, education to retail.

While C-Bay is known for its product breadth and reliability, its secret to success has always been its agility. And nowhere is that agility more visible—or more strained—than in the company’s Software Development Division.

The Software Development Division: C-Bay’s Innovation Engine

This division builds and maintains the custom software platforms that power C-Bay’s enterprise solutions. The work here includes:

• Web-based business platforms
• Mobile apps for field operations
• Internal process automation tools
• API-driven services for hardware integration
• Custom builds for key enterprise clients

Over 40 professionals—developers, designers, analysts, testers, and project managers—keep these systems evolving to meet client needs.

But lately, the workload has grown faster than the team. Agile sprint plans are overbooked. Key deliverables are delayed. And high-value initiatives are sitting in the backlog because the internal staff simply can’t stretch any further.

Leadership has made a decision: strategic outsourcing is no longer optional—it’s a priority.

Your Role: Leading C-Bay’s Outsourcing Push

You’ve been brought in as a project lead within a special initiative inside the Software Development Division. Your task is to help C-Bay develop and implement a modern, efficient outsourcing strategy—across multiple projects and partners.

Your role will evolve across several scenarios, but your core responsibilities include:

• Analyzing current project backlogs and identifying what can be outsourced
• Communicating with internal stakeholders to define needs and constraints
• Creating vendor-facing documents like SOWs and RFPs
• Managing vendor evaluation and selection
• Overseeing project delivery and resolving issues with external teams
• Closing contracts, collecting lessons learned, and recommending improvements

You are not an assistant. You are a decision-maker. And your work will directly impact C-Bay’s ability to deliver for its clients.

Why You’re Being Introduced to C-Bay

C-Bay isn’t just a fictional company for background—it’s the foundation of every milestone and scenario in this practicum.

You’ll be working inside C-Bay throughout the book. Every chapter is designed as a professional challenge drawn from the company’s internal operations. You’ll receive memos, requests, and project briefs from C-Bay’s leaders, just as you would in a real job.

Each milestone you complete—whether it’s planning a procurement strategy, writing an RFP, or evaluating a vendor proposal—will be set within a realistic, evolving C-Bay context. This gives you:

• A cohesive story to follow across multiple deliverables
• A business environment that reflects cross-functional dynamics
• A clear sense of purpose for each task you complete
• The opportunity to develop judgment over time—not just task-level skills

This format helps simulate the complexity of real work. Your decisions in one chapter may affect how you frame or defend a decision in the next. The C-Bay simulation keeps the learning immersive, connected, and professionally relevant.

Division Snapshot: How C-Bay Software Works

C-Bay Software division structure, technologies, operating model, and business constraints.

Function	Details
Platforms Supported	Web, mobile, internal tools, cloud APIs
Methodology	Agile/Scrum with Jira-based sprints
Tech Stack	React, Node.js, Python, Java, SQL, Azure, GitHub, Postman, Figma
Team Size	~40 developers, QA engineers, designers, PMs
Outsourcing Targets	QA automation, UI/UX prototyping, mobile app modules, legacy system refactor
Constraints	Limited headcount, tight deadlines, global client SLAs, IP compliance

Key Stakeholders

Throughout the simulation, you’ll interact (indirectly) with a variety of C-Bay roles. These may appear as memos, chat transcripts, meeting notes, or internal documentation. Treat them like real people. They expect you to:

• Deliver clear, well-reasoned recommendations
• Balance speed, quality, and risk
• Ask smart questions—and not waste their time
• Think strategically while managing the day-to-day details

Stakeholders you’ll likely engage with:

• Director of Software Delivery – owns project timelines and quality
• Product Manager – focused on features, user needs, and market deadlines
• QA Lead – responsible for testing scope and tools
• Procurement Advisor – supports vendor screening and contracting
• Legal Counsel – reviews IP, contract language, and vendor compliance
• CFO or CEO – reviews vendor selection and cost justifications

What This Division Represents

C-Bay’s Software Development Division is under pressure to scale—without compromising its culture of accountability and excellence. Outsourcing has the potential to solve many problems—but only if it’s done right.

You’re being brought in to make sure it is.

With each milestone, you’ll see more of how the division operates, where it struggles, and where you can add value. You’ll learn what it means to lead—not just in theory, but in practice—inside a real business context.