Brief — custom software

The basics

1.What's the company called?

2.What kind of tool should be built?

An internal tool for the teamA CRM / customer managementA dashboard with data and reportsA portal for clients or partnersA SaaS product for other businessesOtherNot sure — I'd like a recommendation

3.What should the software do?

Describe it in your own words — no technical jargon needed.

How it works today

4.How does the process work today?

Who does what, in what order, and in which tools.

5.What's the biggest problem with it?

Pick up to 3.

It takes too longErrors from retyping data by handData is scattered across many placesNo clear view of what's going onThe current tool is too expensive or a poor fitIt doesn't keep up as the business growsOther

0 of 3 selected

6.Which tools do you use today?

Excel / Google SheetsAn off-the-shelf CRMAn ERP or accounting systemEmailPaper documentsSoftware built for usOther

Users and roles

7.Who will use the software?

Management / ownersOffice staffField staffClientsPartners or suppliersOthers

8.How many people will use it?

Up to 1011–5051–200More than 200Not sure yet

9.Should different users have different permissions?

Yes — we need several rolesNo — everyone sees and does the sameNot sure — I'd like a recommendation

10.Which devices will it be used on?

Mainly on a computerMainly on a phoneBoth computer and phoneNot sure — I'd like a recommendation

Scope and data

11.What absolutely has to work in the first version?

A short list works best — the things the tool is pointless without.

12.What would be nice to have, but can wait?

Optional.

13.Should the software connect to other systems?

YesNoNot sure what's needed — I'd like a recommendation

14.Does existing data need to move into the new system?

YesNoNot sure yet

Security and hosting

15.What kind of data will it handle?

Customers' personal dataEmployee dataFinancial dataHealth or other highly sensitive dataDocuments and filesBusiness data only, no personal dataOther

16.Are there specific security or access requirements?

Optional.

Two-factor sign-inSign-in with a company account (e.g. Microsoft or Google)An audit trail — who changed what, and whenData stored in the EUGDPR compliance and a data processing agreementAn audit or certification (e.g. ISO)OtherNot sure — I'd like a recommendation

17.Where should the software run?

In the cloud — no preferred providerWith a specific cloud providerOn the company's own serversNot sure — I'd like a recommendation

18.How will you know the project has succeeded?

E.g. “the report takes a minute instead of a day” or “nobody retypes orders by hand any more”.

Timing and budget

19.When should the first version be ready?

As soon as possibleWithin 3 monthsWithin 3–6 monthsWithin 6–12 monthsNo fixed date

20.What budget do you have in mind for the software?

A rough range is enough — it helps us fit the solution to it.

Under €7,500€7,500 – €20,000€20,000 – €50,000Over €50,000I'd rather discuss it on a call

21.Is there anything else the software should do, or that matters especially to you?

Even a loose idea is useful — you don't need to know the technical term for it.

Answered: 0 of 21

Saved automatically in this browser.