Skip to content
hr (Hrvatski)en

How should you describe what you need?

2 min readUpdated

Describe the problem, not the solution: what gets stuck today, who will use the system, what you use now and how you’ll know the project worked. Add a budget and a timeline. One page is enough; no specification needed.

You don’t need a specification. We need to know where the work gets stuck today, and you know that better than we do. Answer the questions below; we’ll ask about the rest in the first conversation.

What isn’t working today?

“Sales copy the same data from one program into another every day” tells us more than “we need a CRM with a dashboard and API integrations.” The first sentence describes how you work. The second has already chosen a solution, possibly for the wrong problem. If those acronyms mean nothing to you, no harm done: we pick the solution once we know the problem.

Who will use it?

A warehouse worker in gloves and a client on their phone want different things from the same system. Tell us:

  • Who uses it: staff, clients, partners, or a bit of everyone.
  • How many people: three in one office or two hundred across the country.
  • Where they work: at a desk, or out in the field with a phone in hand.

What do you use today?

Tell us how you actually work, not how the process manual says you do. “We keep everything in one shared spreadsheet and nobody dares press Sort” is a good place for us to start: we know what the new system has to replace and what mustn’t get lost on the way.

How will you know it worked?

Write down the change you would notice:

  • Nobody puts the monthly report together by hand anymore.
  • Clients place orders themselves, without calling you.

That sentence becomes the measure we build to.

What does the whole brief look like?

Six answers, one page:

  1. What isn’t working today?
  2. Who will use the system, and where?
  3. What do you use now?
  4. How will you know it worked?
  5. What is the rough budget?
  6. Is there a deadline that won’t move?

Write your answers in the inquiry form, or check off what you recognize in the list below. If you don’t have an answer to one of them, say so; that helps too.

Frequently asked questions

No. We choose the language, the server and the database once we know what the system has to do. If you already use something that has to stay, tell us.

Yes, please. A range is enough. Without one, it is easy for us to propose something too big or too small.

  • Roughly: simple tools €5,000 to €10,000, business applications €10,000 to €25,000, complex platforms from €25,000. We charge no VAT. You get a figure for your system in a free estimate after the first conversation.

  • To the first version in use: simple tools 4 to 8 weeks, business applications 3 to 6 months, complex platforms more than 6 months. You see progress in working software every week or two.

  • Probably, if nobody knows which version of the spreadsheet is the real one, reports take hours to put together, and the same data is copied by hand from file to file.

Tell us where it gets stuck.

Instead of spreadsheets and separate tools, one system shaped around the way your business works, with the server and network beneath it. You can keep the spreadsheets if you insist.

In your own words

Short or detailed, whichever is easier. We read all of it.
The first conversation is free, and we reply within 24 hours.

Write an inquiry

Or write to info@techcraft.hr, WhatsApp or Telegram.