How an E-commerce Enablement Company Increased Business Capacity With a Smaller Technology Team

01The constraint

The team had a capacity problem, but adding people would not have solved the underlying issues.

Engineers needed clearer priorities. Management needed better visibility into outcomes. Product decisions needed stronger business context. The team also needed a way to communicate and coordinate with other departments without creating more management overhead.

At the same time, the company had operational work that still depended on people. Their operations and finance/accounting team spent time on repetitive administrative workflows. Infrastructure carried costs that had not received a proper audit. Fulfillment also faced return-to-sender rates that directly affected margins.

The business needed its technology function to create leverage across these areas.

02The context

The company operates a technology-driven e-commerce business where engineering supports both the company's internal operations and the tools that sellers use to run their businesses.

Before Scale XY's involvement, the technology team had more people but struggled to turn that capacity into consistent business outcomes. Too many initiatives competed for attention. Engineers focused on producing outputs without enough connection to the business problems behind the work. Communication across teams created friction, software quality suffered, and management had limited visibility into what engineering was actually delivering.

The company then reduced its engineering team from six to two engineers.

The company needed the smaller team to keep the business moving while building a stronger way of working around it.

03How we approached it

Scale XY embedded into the organization and took responsibility across technology leadership, product thinking, architecture, management, development, and operations.

We started with prioritization. The team needed to decide what mattered to the business before deciding what to build.

Scale XY worked with the remaining engineers to break work into smaller pieces, establish clearer ownership, improve communication with other teams, and ship alongside them when additional capacity was needed.

The goal was to build a team that could operate with less oversight. Engineers learned to evaluate business needs, decide what to build, break down the work, and communicate their decisions with other departments.

We also looked beyond the engineering backlog.

We identified workflows that could move from manual administration to automation, reviewed infrastructure costs, improved the systems supporting e-commerce growth, and developed AI tools that could handle parts of customer and seller operations.

That widened the scope from managing a smaller engineering team to improving how the company used technology across the business.

04What we changed

The remaining engineers became more autonomous and developed stronger product judgment. They could make better decisions about what to build, understand the business context behind requests, break work into manageable pieces, and work directly with other teams.

The company also reduced its dependence on manual operational work. Eight workflows across Accounting and Seller Success now reclaim approximately 600 hours of work each year. Those hours give the teams more capacity for growth-facing work without adding headcount.

A review of the AWS environment reduced daily usage cost by 27.7%, creating a $763 monthly reduction and approximately ₱563,000 in annualized savings. The review also identified four additional savings opportunities.

Operational improvements reached the sales and fulfillment side of the business as well. Return-to-sender rates fell from 31.8% to 21.7% between June and July, while returned orders fell from 834 in March to 415 in July.

The team also shipped new growth infrastructure, including a self-serve storefront, reusable sales pages, a lead-generation page, and SEO foundations. New storefront and page requests could move from request to shipment within days rather than requiring a fresh build each time.

On the customer operations side, an internal Ecommerce Agent is implemented and improved. The system could answer product questions, take orders, validate information, and prevent orders for unavailable product variations.

By July, the technology team averaged less than one day of cycle time while supporting a broader set of business improvements.

05Technology

Scale XY combined embedded technology leadership, custom software development, workflow automation, infrastructure optimization, and AI tools within the company's existing operations.

The work connected technology decisions directly to the company's operating and financial priorities.

06What we'd tell you again

A smaller technology team forced the company to become more selective about where it spent engineering capacity.

That discipline created benefits beyond faster delivery. Clearer product decisions improved the autonomy of the remaining engineers. Automation reduced administrative work. Infrastructure cleanup reduced recurring costs. Better operational workflows protected margins. New systems gave the commercial teams more room to grow.

The engagement showed how a technology function can create capacity across a business when it works from business priorities rather than from a backlog alone.