top of page
Search

The Minimum Viable Stack: Building Digital Infrastructure Without Drowning in Apps

Updated: 6 hours ago

Part 2 of 4 - Technology Without Hype


Consider a mid-sized non-profit running livelihood and health programs across three provinces. Over six years, it has accumulated a project management tool that half the team uses, a second one that finance insists on, a shared drive with three different folder structures left behind by three different program officers, an accounting spreadsheet that only the outgoing finance manager fully understands, and a WhatsApp group that has quietly become the organization's real system of record — the place where decisions actually get made, even though nothing there is searchable six months later.


None of these tools was a bad choice in isolation. Each solved a real problem at the moment someone adopted it. But the organization never stepped back to ask what the whole stack needed to do together. When a well-liked program coordinator left last year, three weeks of institutional knowledge — passwords, undocumented workarounds, the unwritten logic of which spreadsheet was actually current — left with her. The team spent the better part of a month reconstructing what she alone had known.


This is not a story about a poorly run organization. It is a story about what happens, almost by default, when digital tools are adopted one urgent problem at a time, without a shared view of the whole.


If Part 1 asked whether non-profits are digitally capable enough to serve digitally capable beneficiaries, Part 2 asks a more immediate question: what is the smallest set of tools and habits a small non-profit actually needs to operate on a stable footing - and how do you build it without either standing still or collecting a graveyard of apps nobody fully uses?

The Myth of the Complete Stack

There is a persistent idea, often reinforced by well-meaning technology vendors and donor capacity-building grants, that digital maturity means having a tool for everything: a Stakeholder management system (eg CRM), a project management platform, a learning management system, a dedicated M&E (Monitoring and Evaluation) dashboard, an HR information system, an accounting suite. Each addition is easy to justify on its own. Together, they add up to something few small organizations can actually sustain.


This is not only a non-profit problem. Recent research on organizational technology use found that the typical non-profit now runs three to five or more separate systems beyond its core donor or beneficiary database – and that the deciding factor for effectiveness in 2025 was not how many tools an organization had, but how well the tools it kept actually worked together. For a well-resourced institution with a dedicated IT function, that complexity is manageable.



For a ten-person non-profit where the program director also approves invoices and the finance officer also manages the website, each additional disconnected tool is a small tax on everyone's time.


The result is a familiar pattern across the sector: tools acquired to solve a moment's problem, rarely retired, rarely integrated, each with its own login, its own partial data, its own person who "just knows how it works." Staff quietly route around the official system and default to whatever channel is fastest – usually a messaging app.


The goal of this post is not to add another tool to that list. It is to help you decide, deliberately, what belongs on it, and what doesn't.


Defining "Minimum Viable" for a Non-Profit Context

The idea of a minimum viable product comes from the startup world: build the smallest version of something that lets you learn and operate, then add complexity only when there is clear evidence you need it. Applied to non-profit digital infrastructure, a minimum viable stack is the smallest set of tools and processes that lets your organization reliably do five things:

  1. Communicate and coordinate – know what is happening, who owns it, and by when.

  2. Keep institutional memory – store documents and decisions somewhere that survives staff turnover.

  3. Manage money responsibly – track, approve, and report on funds with a clear audit trail.

  4. Manage people fairly – handle contracts, leave, and basic HR record-keeping without relying on one person's memory.

  5. Protect access – control who can get into what, and revoke that access cleanly when someone leaves.

    Notice what is deliberately absent from this list above: beneficiary-facing service delivery channels, which we address in Part 4, and structured program data and systems which are the subject of Part 3. This post focuses on the internal operating layer – the foundation that Part 1 argued most organizations try to skip in their rush toward more visible digital ambitions.


A minimum viable stack is not a permanent stack. It is the version your organization can run competently today, built with enough discipline that adding complexity later is a deliberate upgrade rather than a patch on top of chaos.


The Five Categories, and What "Minimum Viable" Looks Like in Each

The table below is a starting framework, not a rigid guideline or prescription. The specific tools matter far less than having a clear, single answer in each category – and ideally, everyone on the team knowing what that is.


Category

What it needs to do

A workable minimum viable baseline

The failure mode it prevents

Communication & coordination

One place to see what’s happening and who owns it

A shared email domain plus one lightweight task/project tool (e.g., a free-tier board like Trello or Asana) used consistently for anything beyond a single conversation

Decisions living only in chat threads, invisible to anyone not in that specific group

Documents & institutional memory

Anyone authorized can find the current version of anything

A single cloud drive (e.g., Google Workspace or Microsoft 365) with an agreed folder structure and naming convention, documented in one page

Multiple “final_v3_reallyfinal” files, and knowledge trapped in one person’s inbox

Financial operations

Track, approve, and report on funds with a clear trail

Cloud-based accounting software appropriate to your size (even simple tools like Wave or a well-structured, access-controlled shared spreadsheet with defined approval steps)

An unauditable spreadsheet only the finance officer understands

People operations

Manage contracts, leave, and basic records fairly and consistently

A shared, access-controlled staff record (a structured spreadsheet or a low-cost HR tool) with clear leave and onboarding/offboarding checklists

Verbal agreements, missing contracts, and HR knowledge that leaves when a manager does

Access & security

Control and revoke access cleanly

A password manager for shared logins, plus a written offboarding checklist that includes revoking access, not just returning equipment

One departing staff member taking the only copy of every password with them

A note on the middle column: notice that none of these baselines require enterprise software or a dedicated IT budget. Most can be run, at a genuinely functional level, on free or low-cost tiers of widely available tools. The constraint most organizations face is rarely the cost of the tools. It is the absence of a decision about which tool is the *authoritative* one, and the discipline to actually use it that way.


Sequencing Matters: Process Before Procurement

The most common mistake in building a digital stack is buying / adopting a tool before deciding what the underlying process should be. A new project management platform will not fix an organization that has never agreed on who has decision authority over a given task. A new accounting tool will not fix a finance process that has no defined approval chain. The tool simply digitizes whatever ambiguity already existed, often making it harder to unwind because now the ambiguity is baked into a system with its own logic.


This is, at heart, a governance question as much as a technology one. Before evaluating any tool, it is worth your leadership team spending an hour answering three questions on paper, with no software involved:


  • Who decides what, and who needs to be informed but doesn't decide? Most non-profits have never written this down for their day-to-day operations, even when it is clear for board-level governance.

  • What information does this process actually need to produce, and for whom? A financial approval process exists to protect the organization and satisfy funders – not to generate the most detailed spreadsheet possible.

  • What does "done" look like, and who confirms it? Ambiguity here is what causes staff to default back to asking in the group chat, regardless of which official tool exists.


    Only once these questions have real answers does it make sense to ask which tool should hold that process. Organizations that reverse this order – tool first, process second – tend to end up with expensive software running on top, while the same undocumented habits it was meant to optimize remain, reducing success of tool adoption.


The Single Point of Failure Problem

Every non-profit has at least one version of the departing coordinator described at the start of this post: the person who, without anyone quite deciding it should be this way, becomes the sole holder of a piece of institutional knowledge. Often it is whoever is most comfortable with technology – frequently a younger staff member, sometimes the founder, occasionally whoever happened to set up the email accounts years ago.


This concentration of knowledge is one of the more serious operational risks a small non-profit carries, and it compounds the more digital tools an organization adopts without documentation. A stack built entirely on one person's tacit knowledge is not more resilient than no stack at all. Hence this is hardly a talent management footnote.


What Can Be Done: Three habits reduce this risk without requiring new software:

  • Write down the boring things. A one-page document listing which tool is authoritative for what, who has admin access, and where passwords live is unglamorous and consistently the highest-value document a small organization can create. It should be reviewed, not just written once and forgotten.


  • Treat digital competence as a shared organizational capability, not an individual trait. If only one person can restore a file, reset a password, or explain why the budget spreadsheet is structured the way it is, that is a capacity gap – the same category of gap the sector readily recognizes in program skills, but is slower to recognize in operational ones.


  • Build offboarding into the process from day one. A clear checklist – revoke access, transfer document ownership, hand over admin rights, update the shared knowledge document – protects the organization regardless of whether a departure is planned or sudden, and regardless of how well the relationship ends.


None of this requires an IT department. It requires leadership deciding that operational knowledge is an organizational asset, not a personal one. Building these modest habits can be useful to develop good habit and track organizational asset.



A Practical Selection Framework

When it does come time to choose or replace a tool in one of the five categories above, four questions, tend to prevent the most common regrets:


  1. Does it work on the connectivity and devices our staff actually have? A tool that assumes constant broadband and a laptop for every user will quietly fail for field staff working from a shared phone and intermittent mobile data, regardless of how capable it is in a demo.

  2. Can our least tech-confident staff member use it without a training program? If adoption depends on extensive onboarding you don't have capacity to deliver and sustain, the tool will fail in practice even if it succeeds in the pilot.

  3. Can we get our data out if we ever need to leave? Tools that make it difficult to export your own documents, contacts, or financial records create a second, quieter form of the single-point-of-failure risk – this time held by a vendor instead of a person.

  4. What does it cost at the size we'll be in two years, not just today? Many free or discounted non-profit tiers scale sharply once staff or data volume crosses a threshold. It is worth understanding that curve before committing a workflow to it.

    Cost is deliberately the last question, not the first. A free tool that nobody adopts is not actually cheap. It is an expensive decision that happens to have no invoice attached to it.



Moving Forward

A minimum viable stack is not a finished state. It requires some discipline: to choose deliberately, to document what you choose, to protect against concentrated knowledge, and to resist the pressure (from vendors, well-meaning donors, your own team's enthusiasm after a good webinar) that adds complexity faster than your organization can absorb it.


Done well, this foundation is what makes everything in the rest of this series possible. The data habits in Part 3 depend on people trusting where information lives. The beneficiary-facing delivery channels in Part 4 depend on an organization that can coordinate reliably behind the scenes before it tries to extend that reliability outward.


A reflection before Part 3:

Pick one category from the table above - communication, documents, finance, people, or access - and ask honestly:

if we lost our most digitally confident staff member tomorrow, would this still function? If the honest answer is no, that is not a reason for alarm. It is simply the most useful place to start.

Continuing the dialogue:

What does your organization's digital stack actually look like once you count every tool honestly - including the ones nobody officially approved but everyone quietly uses? We would welcome hearing about it, and about what has and hasn't worked as you've tried to simplify.


About This Series

Technology Without the Hype is a four-part series from Huse Infinity exploring practical digital capability for non-profit organizations across Asia. It is written for leaders and practitioners who are serious about building more resilient, effective organizations – without the jargon, and without the assumption that every problem needs an app.


Huse Infinity partners with non-profits across Asia on consulting, capability building, and governance. If you would like to discuss what digital transition looks like for your organization, we would welcome the conversation.


bottom of page