Business first, software second: understand your process before you pick a system

Why not start with the software?

Because technology only helps when it solves the right problem. Two companies in the same industry can sell the same thing and work very differently: one builds to order and the other builds to stock, one offers credit and the other gets paid upfront. Every business has its own logic, and a system that ignores it gets in your team’s way instead of helping.

That’s why we don’t believe in copy and paste. When someone reaches out to us, we don’t start with screens, apps or tools. We start with you: how you run your business, what eats up your time, which decisions you make over and over and what weighs on you the most.

What does starting with the technology cost?

It rarely shows up in the quote. You pay for it later, in change requests, rework and features nobody uses. In 2014, the Project Management Institute (PMI) found that nearly half (47%) of unsuccessful projects missed their goals because of inaccurate requirements management, meaning how well the project pinned down and tracked what it had to solve.

And the later a misunderstanding is caught, the more it costs. A NASA study found that fixing a requirements error once the system is already in operation costs 29 to more than 1,500 times what it would have cost to fix on paper. The estimate assumes projects like a spacecraft or a military aircraft, so don’t take the numbers literally, but the logic holds: fixing a sketch costs a conversation; fixing a system your team already uses costs rework and retraining.

What’s the difference between the what and the why?

The what is what you ask for: “I want an inventory system,” “I need an app.” The why is the problem behind it. If someone builds the what without understanding the why, you can end up with a well-made system that automates exactly what should have changed.

In 1990, Michael Hammer wrote in Harvard Business Review that heavy investments in information technology had delivered disappointing results because companies only used it to speed up their old ways of working. One of his examples is Ford, whose accounts payable department in North America employed more than 500 people. The plan was to cut that by 20% with new systems. But Mazda’s department had 5 people, and even after adjusting for size, Ford figured its own was five times bigger than it needed to be.

When Ford looked at why, it found that most of the time went into sorting out mismatches between the purchase order, the receiving record and the invoice. Instead of investigating them faster, Ford changed the process so they wouldn’t happen: the order is entered once, and receiving confirms it when the goods arrive. Where the change was in place, the department needed 75% fewer people, not 20%. The what was “a system for accounts payable.” The why was “mismatched paperwork eats up our day.”

How do you describe your process before talking to a vendor?

You don’t need diagrams or technical terms. One page is enough, answering these questions the way you’d explain them to a new hire:

1. What do you want to fix, and how do you notice it today? “We forget orders” is a good start; “we forgot three orders last month” is better.
2. How does it work today, step by step? From the moment a request comes in until it’s paid: who does each step, where they record it (Excel, WhatsApp, a notebook) and what document comes out.
3. Why does each step exist? If the answer is “because we’ve always done it that way,” flag it. That’s usually where there’s room to improve.
4. What decisions do you make every day? What to buy, what to produce first, who gets credit, and with what information.
5. What makes you different? What your customers value and you don’t want to lose by bending to generic software.
6. How will you know it worked? One or two numbers: fewer forgotten orders, same-day reports, fewer hours of data entry.

For more detail, try the real-order exercise in 7 signs your business has outgrown Excel or document your processes. Don’t wait until it’s perfect. One honest page is enough.

What does a good first conversation with a vendor look like?

It’s one where the vendor asks more than they pitch. If they’re showing you screens or quoting a price in the first few minutes, they don’t understand your business yet.

Good questions go after the why. Toyota turned this into a method, the 5 Whys: asking why again and again until you get past the symptom to the root cause. As the Lean Enterprise Institute notes, the number five isn’t the point; what matters is not stopping before you reach the cause. For example:

• “I need an app for my sales reps.” Why?
• “Because orders come in wrong.” Why do they come in wrong?
• “Because every rep has a different price list.” Why?
• “Because prices change every week and nobody tells them.”

The real problem wasn’t the app. It was having one up-to-date price list. Maybe you still need the app, but now you know what it has to solve.

To compare contracts, data and support, use our 10 questions to ask before hiring a custom software company.

What does a system that understands your business look like?

You can tell by the details no generic software would include. Three examples from our projects:

• [Cleanly](/en/projects/cleanly-plataforma-servicios-limpieza) coordinated cleaning services through calls and messages. Beyond the schedule, there were two underlying problems: there was no evidence to settle disagreements about quality, and taking cash was a risk. So every job closes with before-and-after photos, and payment is held until the work is done.
• [Verdict](/en/projects/verdict-revisor-expedientes-legales) is for lawyers who reviewed thousands of documents one at a time. For confidentiality reasons, nothing could be uploaded to the cloud, so everything runs offline on their own computers.
• [CelMex Unlockers](/en/projects/celmex-unlockers) needed to track every order in real time and connect deeply with its suppliers, something off-the-shelf platforms couldn’t do.

We also don’t build things just so they look pretty. For Translate3D, for example, the entire experience was worked out in design before any code was written, with clarity and conversion in mind, not decoration.

How does Nightly work?

Business first, technology second. In practice, that’s three steps:

1. Free consultation. You talk with the founders, in person in the Bajío region or by video call, and we figure out what to tackle first. If cleaning up a process or using a tool that already exists is enough, we’ll tell you.
2. Written proposal. With the scope, the price of each stage and its dates, so you know what’s included before you decide.
3. Delivery in stages. Urgent issues get solved in hours, and most projects are ready in about a week. Large systems are delivered in stages, each with its date in writing.

Does your current technology understand you, or does it just get in the way? Let’s talk. In a free consultation, we start with your business, not the software. See how we approach custom software development. Pricing depends on scope, and we send it to you in writing after the consultation.