UNDERSTAND THE WORK BEFORE BUILDING

Web application questionnaire

Help us understand your process, users and first useful version. The result is a structured project summary and open questions, without an automatic price.

A CLEAR START, AT YOUR PACE

Tell us how your work could improve.

Allow around 15–30 minutes to describe your project at a comfortable pace. Your answers help us understand what you need and prepare a more useful proposal.

You do not need technical knowledge. Where offered, “Not sure” is a valid answer. At the end, you can review and edit everything before sending.

These answers prepare our conversation and an individual proposal for your application. There is no automatic price.

The time is approximate, with no countdown. Completing this questionnaire is not an order and does not send an enquiry.

Confirmed answers are temporarily kept in an encrypted server session tied to this browser after the server acknowledges saving. A validated save sets a new 30-minute draft limit; simply reading does not extend it. This is not permanent storage or a way to resume on another device.

Without JavaScript, all questions are shown below. Answer follow-ups only when applicable, then use Review all answers. Server validation, editing, language changes and TXT download remain available.

Fields marked with * are required for review. Other answers help clarify the scope; “Not sure” is welcome where offered.

Describe processes and types of information. Never enter passwords, access keys or real personal records of patients or clients.

The language buttons in the header keep your current answers when switching language.

The problem and current workflow

Required

What would you like to improve?

Describe the business problem and why it matters.

Required

How is the work done today?

Who does what, and where is information recorded?

Optional

Which tools do you use today?

For example: spreadsheets, email, an application or paper records.

Optional

One typical case, step by step

Start with the trigger and finish with the expected result. Use fictional examples.

Optional

Where do delays, errors or repeated entry occur?

Where does work get stuck or information get entered twice?

Users and responsibilities

Required

Who will use the system?

User groups, such as employees, managers or clients.

Optional

Approximate number of users

Include simultaneous use if known. A rough estimate is enough.

Optional

Locations

How many locations, and do they work differently?

Optional

User roles

For example: operator, reviewer and administrator. Describe responsibilities, not people.

Optional

Who can view, enter, edit or approve data?

Give an example of an important access restriction.

Optional

Must data stay separate between companies or locations?

For example: a branch may only see its own records.

Answer only when this choice applies.

Optional

How should data be separated?

Which groups may share information, and which must remain separate?

The business process

Optional

Process steps

Describe the sequence from receiving a request to completing work.

Optional

Statuses

For example: received, in progress, awaiting approval and complete.

Optional

Who approves changes?

What needs approval, and are several approval levels involved?

Optional

What happens after an error, rejection or return to an earlier step?

How should work recover, and who needs to know?

Optional

Is a change history needed?

A record of who changed agreed information and when.

Optional

Are notifications or reminders needed?

For example: before a deadline or when approval is needed.

Answer only when this choice applies.

Optional

Which notifications, and when?

The trigger, recipient role and preferred channel.

Data and connections

Optional

Types of data and documents

Categories only. No real patient/client records, passwords or access keys.

Optional

Should existing data be transferred?

Moving agreed data from the current tool to the new system.

Answer only when this choice applies.

Optional

Where are the existing data, and in what format?

Describe source and volume. Do not paste actual records.

Optional

Should other systems connect?

For example: accounting software or an existing application.

Answer only when this choice applies.

Optional

Systems and information to exchange

Systems, exchange direction and frequency. No credentials.

Optional

Is a documented API available?

An API defines how systems exchange data. “Not sure” is a valid answer.

Optional

Views and reports

What should each role be able to see or compare?

Optional

Exports

For example: a spreadsheet-compatible report or PDF, and who needs it.

First version and collaboration

Required

What is essential for the first version?

The smallest useful scope that improves the current workflow.

Optional

What can follow later?

Separate future ideas from the first version’s essential work.

Optional

Preferred deadline

A month, date or “Not sure” is enough. Delivery dates are agreed separately.

Optional

Who makes project decisions?

A responsible role or your own name, without other people’s private details.

Optional

Who will help check the first version?

The roles involved and their availability.

Optional

Indicative budget, optional

Helps us discuss priorities. It does not change the price of the same scope.

A way to reply

Contact details are optional for review. Your name and email are required only if you choose to send.

Optional

Your name

A contact person for this enquiry.

Optional

Your email address

Used for replies; required only when sending a questionnaire.

Optional

Company, optional

Your company or organisation name.

Optional

Phone, optional

Include the country code if useful.

Temporarily keeps current answers in this session, including incomplete forms. It does not send an enquiry.

Answers are temporarily kept in an encrypted session for review, editing and language changes. The draft expires after 30 minutes. Discard removes it; expired session files are removed during server cleanup. There is no permanent draft storage.

Web application questionnaire

Tell us how your work could improve.

A way to reply

Tell us about
your project.

Your summary is ready.

Website example