पाठशाला Pathshala · संचालन Sanchālan, Operations · Lesson 07 · Start

The tool stack for the first year

Four systems hold a company’s memory: the ledger, the customer record, the conversation and the documents. Choose those four for fifty people. Everything else can be swapped on a Friday afternoon.

Pathshala, The Founder Library · 11 October 2026 · 7 min read

Tools and supplies arranged on racks and benches in a tidy workshop in Malta. — Photograph: Tom Fisk · Pexels

The tools chosen in the second month of a company are usually still running in its fifth year. Nobody decides that they should be. They simply hold too much of the company’s history to move, and the day a founder finally tries to move one is the day an audit, a fundraise or a key resignation makes it hardest.

This lesson separates the four systems that are expensive to replace from the dozens that are not, sets out what each of the four must do in India, gives a test every tool should pass before the company pays for it, and ends with the quarterly review that keeps the stack from growing in the dark.

The four systems that hold the company’s memory

A design tool, a password manager, a video-call app and a survey form can each be replaced by a better one in an afternoon, because what they hold is either small or recreated every week. Four systems are different. Accounting holds every rupee the company has earned, spent and owes, and the law requires it to be kept for years. The CRM holds every customer, every conversation and every deal, which is the only record of why revenue is what it is. Communication holds the day-to-day reasoning of the team. Documentation holds what the company decided and how it does things. Each of the four is a system of record: when two people disagree about a fact, it is the one they open.

The rule that follows is simple. Spend a week choosing each of the four, and choose for a company of fifty people even if there are five. Spend ten minutes choosing everything else, and expect to change it. The cost of a wrong choice is not the subscription. It is the migration: three years of ledgers re-entered during an audit, a customer history rebuilt from inboxes, or a year of decisions that now exist only in the memory of the person who left.

Accounting: the one the law chooses for you

An Indian company has less freedom here than anywhere else in the stack. Section 128 of the Companies Act requires books on an accrual basis and by double entry, kept for eight financial years. Since 11 August 2022 the Companies (Accounts) Rules require electronic books to remain accessible in India at all times, with a daily backup on servers physically located in India and the provider’s details reported to the Registrar each year. For financial years from 1 April 2023 the software must record an audit trail of each and every transaction, keep an edit log with dates, and ensure the trail cannot be disabled; the statutory auditor reports on whether it ran all year.

Two further requirements arrive with growth, and the software should handle them before they arrive. Once aggregate turnover exceeds ₹5 crore in any financial year from 2017–18, B2B invoices must be reported as GST e-invoices, a threshold in force since 1 August 2023. And TDS on vendor payments, which starts with the first contractor, has to be computed at accrual and reconciled every quarter. Software that cannot do either forces a spreadsheet beside it, and a spreadsheet beside the ledger is where errors live.

The practical choice for most Indian startups is between a ledger the chartered accountant already runs on their own machines and a cloud ledger the founders can open from a phone. Either works if four conditions hold: the company owns the licence and the data file, the CA is a user on the company’s system and not the other way round, the audit trail and India backup are confirmed by the vendor in writing, and bank and payment-gateway feeds come in automatically. The [bookkeeping lesson](/library/bookkeeping-from-day-one) covers what goes inside.

CRM: the customer record the company owns

Every founder starts the customer record in a spreadsheet and should. A sheet with one row per account, a stage column, the next step and a date is a CRM, and it will serve until either a second person starts selling or the open deals no longer fit on one screen. At that point move, once, to a tool that will hold a sales team of ten.

Three properties matter more than features. The record belongs to the company: every salesperson works inside the company’s account, and a deal is never tracked in someone’s personal phone or private sheet. The record is complete: emails and calls are logged automatically or not at all, because manual logging decays within a month. And the record agrees with the ledger: the customer name, the invoice and the deal value are the same in the CRM and in accounting, which means the two are connected or the names are entered once by the same rule. A CRM whose revenue figure never matches the books will be ignored by the person who matters most, the founder reading the [monthly report](/library/monthly-close-and-mis-report).

Communication: a company workspace, not a personal phone

Much of Indian business runs on WhatsApp, and a startup’s first customers will expect to reach it there. That is fine for the conversation with a customer. It is not fine for the company’s internal work, for one reason: the groups belong to the phones of the people in them. When a sales lead leaves, the history of every account they managed leaves in their pocket, and the company cannot remove them from groups it does not administer.

So internal conversation moves to a workspace the company owns, with an admin who can add and remove people, enforce two-factor sign-in and keep history. Customer conversations on WhatsApp move to a business account the company controls, with more than one person able to answer. Email stays for anything external and formal. And the rule that matters most is about what chat is for. Basecamp’s guide to how it communicates puts it in four words: writing solidifies, chat dissolves. Chat is for coordination that will not matter next month. Anything that will, goes in the fourth system.

Documentation: the system that remembers

The documentation tool is the one founders choose last and regret most. It should be a single searchable place where every page has an owner and a date, where decisions are written as memos and kept, and where how-the-company-works pages are edited rather than duplicated. GitLab, which runs one of the largest public company handbooks, describes the practice as handbook first: write the answer down first, then communicate the link, so there is a single source of truth. A five-person company does not need GitLab’s handbook. It needs the habit, and a tool that will still hold the pages when there are fifty people reading them. The [writing culture lesson](/library/writing-culture-decisions-in-documents) covers what goes in.

One more constraint has a date on it. The Digital Personal Data Protection Rules were notified on 13 November 2025, and most of the Act’s obligations on businesses, including notice, consent and breach reporting, apply from 12 May 2027. Every tool in the stack that stores a customer’s name, phone number or address is part of that obligation. The documentation tool is where the list of those tools should live.

A tool is cheap to buy and expensive to leave. Test the leaving on the day you sign up, while there is nothing to lose.

The stack at fifty people: what changes and what does not

Take a Pune company of seven people in its first year: a cloud ledger with the CA as a user, a spreadsheet CRM, a company chat workspace, a shared drive and one wiki. At fifty people, two years later, the ledger is the same ledger with three more users and an approval workflow for payments; the spreadsheet has become a CRM with nine salespeople in it, migrated once in month eleven; chat is the same workspace with forty more seats; the wiki has four hundred pages and an owner for each section. What changed was seats, permissions and one deliberate migration. What did not change was where the history lives.

Vintage hand tools on a wooden workbench lit by a window. — Some of these tools are older than the people who use them. The ones a company keeps for years are the ones that hold its history. Photograph: Christopher Moon · Pexels

The bill changes too, and it is the item founders notice last. A stack of twelve per-seat tools that cost little at seven people is twelve times fifty seats at fifty people, and nobody decided to spend it. Write the fifty-seat price of each tool next to today’s price on the day you sign up, and the budget conversation at forty people will not be a surprise.

The quarterly tool review

Once a quarter, in the week after the monthly close, one person spends forty-five minutes on the stack. Pull every software charge from the company card and bank statement for the quarter and list each tool with its owner. Compare seats paid for with people employed, and remove the seats of anyone who has left. Check the last sign-in of every user who still has access to the four systems of record. Re-run the exit test on one of the four, in rotation, by exporting its data and opening the file. Cancel anything nobody claims. Then update the page in the wiki that lists every tool, who owns it, what personal data it holds and what it costs at fifty seats. The review takes less time than one migration meeting, and it is the only way the stack stays chosen rather than accumulated.

Nothing here is legal, tax or investment advice. Statutory requirements are stated as checked on 11 October 2026; confirm with your chartered accountant which apply to your company.