We built AgencyOS for a recruitment operation that was running its entire pipeline — candidates, client deals, document generation, team performance — through WhatsApp groups and Excel sheets. That's not an unusual starting point in Bangladesh. It's the default one. Most Bangladeshi SMEs, and a fair number of larger companies, run core operations on some combination of spreadsheets, WhatsApp, and institutional memory. The interesting question isn't why that happens — it's why it persists even at companies that can clearly afford better, and what actually breaks the pattern.
It's not that off-the-shelf software doesn't exist
There's no shortage of CRM, ERP, and workflow tools available to a Bangladeshi business in 2026 — global SaaS products are a signup away, and a growing number of local players build specifically for the Bangladeshi market. The actual barrier is fit: a global CRM built for a US sales team assumes a workflow, an approval chain, and a set of business rules that don't map onto how a Bangladeshi recruitment agency, garment exporter, or logistics operator actually works. Someone still has to reshape the tool around the business, or reshape the business around the tool — and most companies, understandably, don't have the internal capacity to do either. So the spreadsheet stays, because the spreadsheet has no opinion about how the business should run. It just holds whatever you put in it.
Custom software has a reputation problem it mostly earned
Ask most Bangladeshi business owners about custom software and you'll hear a version of the same story: a six-month engagement that became a fourteen-month engagement, a vendor who disappeared after the invoice cleared, a system that technically shipped but nobody on staff actually uses because it doesn't match how the team actually works. That reputation is earned, not paranoid — we hear a version of it in nearly every first conversation with a new Bangladeshi client. It's also exactly the failure mode we build against: sprint-based delivery where the client sees working software in week two, not a requirements document in month three, and fixed-scope engagements that end in full code ownership rather than an open-ended retainer designed to keep them dependent on the vendor.
The actual trigger is usually a growth-stage breaking point, not a strategic decision
Companies rarely decide to modernize their operations proactively. What actually happens is a growth-stage breaking point: the WhatsApp group hits a size where nobody can find anything anymore, a client relationship gets damaged because two team members double-booked the same deal, a compliance requirement shows up that a spreadsheet genuinely cannot satisfy. That's the moment a business becomes receptive to replacing its informal systems — not because someone read an article about digital transformation, but because the informal system just visibly failed in front of them. We scope faster and more concretely with a client who's already felt that pain than one who's exploring modernization abstractly, because the failed workflow is right there to design against.
What actually gets a Bangladeshi SME off spreadsheets
- Software shaped around the business's actual workflow — including its undocumented exception paths — not a generic template the business has to contort itself to fit.
- Visible working software within the first two weeks, so trust is built on what the client can click through, not a proposal document.
- Full ownership of the resulting codebase and infrastructure, so the client isn't trading a spreadsheet dependency for a vendor dependency.
- A design that keeps working over WhatsApp and mobile-first interfaces where that's how the team already operates — replacing the tool, not the channel, when the channel itself isn't the problem.
The spreadsheet isn't the enemy. It's a rational choice for a business that hasn't yet had a piece of software earn its trust. The fix isn't convincing a company that software is good in the abstract — it's building the specific system that fits how they already work, shipping it fast enough that they can feel the difference within weeks, and leaving them owning it outright when the engagement ends.