Imagi-Tech

Scoping quiz

What are you actually asking us to build?

"We need software" is where every project starts and no project can be quoted. Seven questions below turn it into a brief: the shape of the build, what the blueprint has to cover, the part that carries the risk, and where to start. Takes about two minutes, needs no email, and you can take the result to any developer you like.

Two minutes, seven questions

Describe the software you actually need

Most people know something is wrong and cannot name the project. Answer these and you get a written brief: what shape the build is, what the blueprint has to cover, and which part is the risky one. No email required to see it, and nothing here quotes you a price.

1 What runs the work today?

The real system, not the one on the org chart.

2 How many people would use it?

Everyone who would touch it in a normal week, including part-time.

3 Where does the work happen?

This decides more about the build than almost anything else.

4 What hurts most right now?

Pick the one that costs you the most hours, not the most annoyance.

5 How much history has to come with you?

Old records are usually the most valuable and most fragile part of a project.

6 What absolutely cannot stop while this happens?

Every project has one. Naming it early is what keeps it safe.

7 When would you want this working?

An honest answer here changes what we would recommend building first.

Not sure on one? Skip it — the brief still works, it just gets less specific.

Why bother

A brief is worth more than a quote

Two developers quoting the same vague request will give you two numbers that cannot be compared, because they are pricing two different projects. A written brief fixes that. It also tends to surface the awkward questions — what happens to the old records, what cannot stop during the switchover — while they are still cheap to answer.

Ours is free, unattached, and yours. If you take it to somebody else, that is a completely fine outcome.

Free audit

Let's get started

Tell us what is not working. Plain language is perfect — "our Access database is dying" tells us plenty.