Name the work that goes wrong
Say what starts the work, who does it and where it slows down or fails. If you cannot describe it in a few sentences, software will not describe it for you.
Fix the problem before you commission the software.
Custom software works best when the problem behind it is clear. These are the points we would ask you to settle first, and a quick way to send us yours.
Six things to settle first.
None of these needs a technical specification. They are the questions that decide whether a build is worth starting.
Agree who owns the process
Someone should be able to decide how the work ought to run. Software built for a disputed process tends to inherit the dispute.
Tidy the information first
Duplicate records, unclear names and missing fields become software problems. Cleaning a spreadsheet is often cheaper than building around it.
List the systems involved
Note the spreadsheets, email inboxes and products that hold the work today. Many problems need a connection between them, not a new application.
Try a smaller change
A better template, a shared inbox rule or an existing product may solve it. Custom software is worth it when none of those fit.
Decide how you will know it worked
Pick one thing you would notice, such as fewer hand-offs or a quicker answer to a customer, before anything is built.
Next step: write down your answers to these six points, even roughly, then send us the problem.
Send us your problem.
One line is enough. A person at Codemind reads it and replies. Please do not include customer names, passwords or other sensitive information.
The quickest route today is email.
Write to [email protected]Not sure which of these applies?
Describe the work and the systems you use. We will tell you honestly whether you need custom software, a smaller fix or neither.