Signs Your Indianapolis Business Has Outgrown Spreadsheets

Count how many of these happened in your business in the last month.

• The same customer details got typed into two or more places.
• Someone keeps "the real spreadsheet", and everyone else works from a copy.
• Staff spent time asking each other where a job or an order stands.
• Two people edited the file at once, and nobody was sure which total was right.
• A formula broke and the numbers were wrong for a while before anyone noticed.
• A customer asked for something the spreadsheet can't give them, like a status or a price.
• You tried a software tool that almost fit, except for the one thing you do differently.
• A new hire needed days to learn how the file works.

Two or three is normal for a growing business. Five or more means the spreadsheet is now doing a job it wasn't built for. The formula problem is more common than it feels: Raymond Panko's review of spreadsheet research reports that 88% of the 113 spreadsheets checked in field audits since 1995 contained errors.

Working out which permits, zoning approvals and licenses a new Indianapolis business needs is the kind of job the Indianapolis Business Journal called intimidating and time-consuming. The city's answer was OpenCounter Indy, a step-by-step online tool that shows which permits you'll need and what they're likely to cost, along with how long the process will take. The City of Indianapolis small business guide points owners to it.

The city didn't write that software from scratch. The IBJ reported that the Indy Chamber paid $36,250 for the project and that OpenCounter began as a Code for America project. The Indy Chamber's announcement says the city set up the Indianapolis version with the Chamber's Business Acceleration Team and offers it in English and Spanish. Trojan had no part in building it. It's here because it's a local example of the first move most businesses should try: buy a tool that does most of the job and set it up for how you work.

Most businesses end up with a mix. They keep an accounting package and a calendar they bought, connect them where a connector exists, and build one small app for the part nobody sells, like a pricing tool or a job board with their own statuses.

Build the screen your team fights with every day, and leave the rest of the system for later. For a lot of offices that's an admin screen over a real database: each job or order as a record, a status that everyone can see, a history of who changed what, and an export button so the spreadsheet can still exist as a report.

That's how our own inquiry pipeline works. Each lead moves through new, contacted, booked, won, lost or junk. Every status change is written to a history table along with who made it, and database triggers stop anyone from editing or deleting those rows. Nobody keeps a side copy, because the record everyone sees is the real one.

What a first build like that costs depends on how many kinds of people log in and what it has to remember. We walk through those drivers in what a custom web app costs in Indianapolis.

1. Freeze the columns. Agree on what each one means and write it down, because half of most migrations is discovering that two people used the same column two ways.
2. Pick one record of truth for each thing, like customers or jobs. Everything else reads from it.
3. Import once, check a sample of records by hand with the person who knows the file best, then stop editing the old file.
4. Keep a read-only copy of the spreadsheet for a month so nobody panics about lost history.
5. Give people an export, so anyone who still wants a spreadsheet gets one that's always current.

If your office hit five or more signs above, talk through the first build with us. The first call is free, and sometimes the answer is to buy a tool.