Short answer. Creating management software means moving from files that get copied to a base where each piece of information is entered only once. There are five routes: a spreadsheet or Access made in-house, a no-code tool, off-the-shelf software configured, an adapted ERP, software developed for you. The choice depends on three things: how many people write at the same time, how particular your rules are, who will keep it alive in three years. Whatever the route, you start with a single chain from end to end, for example from quote to invoice, and not with a list of modules; and with the drawing of the data, before that of the screens.
This page is for the manager of a company of ten to a hundred people whose management rests on files, for the person who built those files and knows they will not hold, and for the founder based in France who wants management they can read from afar for their company in Algeria. The definitions come from public sources: spreadsheet, Access, no-code platform, off-the-shelf software, custom software, relational database, business rule, role-based access control, audit trail, vertical slice, maintenance. The 25-person company, its five files and its calendar are a constructed example. The page gives no prices.
The file that multiplies
The figure shows the same order file six months later, then the same information in a base.
The spreadsheet is not to blame. A spreadsheet is a computer application for computation, organization, analysis and storage of data in tabular form. It does that job very well for one person. It breaks when it serves as a register for several: in the example, the order file has become five files, and the same question (how many orders this month?) gets five answers, from 398 to 421. What the studies say. They estimate that around 1% of all formulas in operational spreadsheets are in error. Add the lack of controls on who can see and modify what, and the difficulty of knowing who changed what, and when. Modern spreadsheets keep a revision history: it helps, without making a register.
Three signs. A file name ending in “v2” or “final”. One person without whom the file no longer opens. A simple question that takes half a day of copying. What a base changes. Each piece of data is kept in one place: that is the single source of truth, where every element is edited in only one place. A relational database arranges information in tables of rows and columns, organised to reduce redundancy and protect data integrity. The customer is written once; the order points to it, it does not copy it. What this page does not cover. Leaving an old piece of software is another job, described in migrating old management software.
«A spreadsheet keeps cells. Management software keeps facts.»
Five ways to get there, and where each breaks
The figure sets the five routes side by side: what each gives, and the point where it gives way.
Access. It is a database management system: it is multi-user and handles record-locking, and is often a good fit for department solutions. Its bounds are known: a desktop database is capped at 2 GB, and the generally accepted limit is 1 GB or less of data. Its real limit is elsewhere: it rests on the person who built it. No-code. A no-code platform supports creating software through a graphical user interface. It suits a form, a tracker, an approval circuit. For large-scale or mission-critical applications, its suitability is still questioned; and you should check, before committing, how your data gets out.
Off-the-shelf, ERP, or developed. Off-the-shelf software is a ready-made product: it can generally be obtained and operated at a lower cost than development, and it is the right choice when your needs are everyone's, as for sales management. An ERP integrates the main processes around a shared database. Custom software is developed for a specific organisation; it is often considered more expensive at the start. But the cost and delay of customising an off-the-shelf product can add up to those of development: that is the point to price before choosing. The practical rule. Standard for what everybody does; custom for what sets you apart; and never two entries between the two.
Creating management software, in six steps
The figure gives the order; the second step, the data, is the one most readily skipped.
A chain, not a list of modules. You do not start with “sales, stock, purchasing, accounting”. You start with a path: for example, from the quote to the invoice paid. Everything that path touches is built; the rest waits. Data before screens. Three kinds of objects describe almost all management: records (customer, item, supplier), documents (quote, order, delivery note, invoice), movements (a stock entry, a payment). For each, two questions: who creates it, only once? Who has the right to change it afterwards?
The rules, said out loud. A business rule defines or constrains some aspect of the business: no delivery beyond the credit ceiling, no discount above a threshold without approval, no invoice without a delivery note. Most often they are written nowhere: they live in the heads of three people. Getting them said, then writing them down, is half the work, and the substance of a useful specification. Taking over what exists. Your files are not thrown away: they become the starting material, cleaned, de-duplicated, imported in rehearsal several times, as in taking over your data.
What management software is made of
The figure stacks five layers; the first is the one that outlives all the others.
The data. It is the layer that outlives everything: the screens that get redone, the tool that gets changed, the provider you leave. Insist on being able to take it with you, in a readable format, at any time. Vendor lock-in is no longer being able to change vendor without substantial switching costs: it is decided here, and in the handover of the code, the subject of the application stuck with a developer. The rules. Business logic is the part of the program that encodes the real-world rules determining how data can be created and stored. It is what refuses a negative stock or a duplicate invoice. And an operation there is complete or has no effect: a half-recorded order does not exist.
Rights and the log. Role-based access control restricts each part of the system to authorised users: the storekeeper sees the stock, not the margins. An audit trail keeps a chronological record of what was done: who changed this price, and when. These are the two things a shared file gives poorly. Screens and reports. One screen per gesture, in the team's language, usable on a phone where the work is done; reports the manager reads without asking for them. After delivery. Maintenance is the modification of software after delivery; the reference article attributes 80 to 90 percent of the lifecycle cost to it. Management software has to be kept alive: see keeping an application alive.
Layer by layer, or slice by slice
The figure builds the same software in two orders: sixteen cells, two weeks each.
Two orders for the same work. In the example, four chains and four layers make sixteen cells. Built layer by layer (all the data, then all the rules), the software advances everywhere and is used nowhere: the sales chain is complete only at week 26. Built slice by slice, it runs at week 8. A vertical slice is a cross-section through all the layers of the software for a single function. What it changes. At week 8, real orders go through. The teams say what is missing. The next three slices are built knowing it.
The first version. It is called a minimum viable product: a version with just enough features to be usable by its first users. For management software, that means one complete chain, not a little of everything. What to ask for. A demonstration at a fixed interval, on your own data. The date of the first usable chain. The way to deliver without breaking what already runs. What to avoid. Six months of development followed by one big go-live: that is the left-hand pattern, the one where you find out on the last day that the discount rule was a different one.
«Ask for the date of the first usable chain, not the end date.»
Eight weeks, in the example
Eight weeks for the sales chain of a 25-person company, one of them for scoping.
- What the manager receives: one complete chain in service; their data in a base they can export; their rules written down; rights per role and a log; the code and the accounts in their name; the plan for the next waves.
- What the company no longer does: copy an order from one file to another, look for the right version, depend on a single person, discover a negative stock, redo the same table at every month end.
- What is measured: number of files still kept by hand; number of re-entries per order; time between delivery and invoice; gaps found during the parallel run; go-live week of each chain.
- What Symloop does: scoping, the data model, building slice by slice, taking over the files, the parallel run, go-live, then the next waves and maintenance.
Scoping. One week: the chain chosen, the files opened one by one, the rules said by those who apply them, the list of users. The slice. Four weeks for the sales chain, shown every week. The take-over. In parallel: customers and items cleaned, balances carried over. The parallel run. Two weeks in which files and software are kept together; every gap is explained, and old errors in the file are often found on that occasion. Go-live. The files become read-only: they are not deleted, people simply stop writing in them.
Afterwards. The next chains come in waves, in the order in which they hurt: stock, then purchasing, then cash. The durations are those of a constructed example: a 25-person company, one chain. More rules, several sites or a difficult take-over need more. When not to develop. If off-the-shelf software does what you do, with no retyping, take it: that is our answer too. Development is justified by what you do differently from the others.
- How do you create management software?
- By starting from one chain end to end, not from a list of modules: draw the data (records, documents, movements), write the rules, build that complete chain, take over your files, then widen. The tool comes after: spreadsheet, Access, no-code, off-the-shelf software or development.
- Can you create management software with Excel?
- For one person and a simple need, yes. As soon as several people write at the same time, the file multiplies into versions. A spreadsheet calculates; it controls poorly who changes what, and does not guarantee that a piece of data exists only once.
- Can you create management software with Access?
- Yes, for a department: Access is multi-user and handles record-locking. Its bounds: 2 GB per desktop database, and a strong dependence on the person who built it. It is an honourable stage, rarely a destination.
- How do you create sales management software?
- Start with the chain quote, order, delivery, invoice, payment, where each document is born from the previous one with no retyping. First check whether off-the-shelf software covers it; develop what is particular in your rules.
- How do you create stock management software?
- With a log of movements: every entry, exit or transfer is a dated line, and the stock is their sum. A table that only keeps the quantity cannot explain a gap.
- Off-the-shelf or custom software?
- Off-the-shelf when your needs are those of your sector; custom when your rules are what sets you apart; often both, connected. Price the customisation of the off-the-shelf product: it can add up to the cost of development.
- How long does it take to create management software?
- In this page's example, eight weeks for a first chain in service in a 25-person company, then one wave per chain. Ask for the date of the first usable chain, not only the end date.
- Which module should we start with?
- With the chain that produces the most retyping or errors today, often sales. Neither the one that looks simplest, nor all of them at once.
- Who owns the code and the data?
- Ask the question before starting. Your data must remain exportable at any time, in a readable format; the handover of the source code and the accounts must be provided for in writing. Without that, changing provider becomes very hard.
- What happens to our Excel files?
- They serve as starting material: cleaned, imported, compared with the software during the parallel run. Then they become read-only. Excel remains useful for analysing an export, no longer for keeping the register.