HOW WE WORK TO GET STARTED

Functional analysis for software projects

Before writing a line of code, we define what needs to be built and how it should work. We start from your business and how you work today, not from technology, and hand you a document to decide with data.

A desk with a process map, wireframes of an application and requirement notes

What we study

01

Processes and workflows

How work is done today, what should change and where the bottlenecks are.

02

Users, roles and permissions

Who uses the system, what each profile needs and what they can see and do.

03

Modules and features

What each part does, both the application users see and the internal back office.

04

Integrations

What data is exchanged with the ERP, CRM, accounting, devices or external services, and in which direction.

05

Non-functional requirements

Usage volume, availability, security, data protection and accessibility.

06

Phases and priorities

What must be there on day one and what can wait, so nothing is overbuilt.

What you get

  • A functional document covering processes, modules, roles and integrations.
  • Sketches of the main screens to validate the user journey.
  • A phased plan with priorities.
  • An effort and timeline estimate for each phase.

When it makes sense

  • You are going to ask several providers for quotes and want to compare them on the same scope.
  • The project spans several departments or systems and nobody has the full picture.
  • You need to justify the investment to management or for a grant application.
  • You already tried the project once and it did not go as expected.
STEP BY STEP

How we do it

  1. 01

    Interviews

    We talk to the people who will use the system and to whoever decides.

  2. 02

    Review of what exists

    Documents, spreadsheets, current applications and the systems to connect with.

  3. 03

    Definition

    We write the document and the sketches and review them with you.

  4. 04

    Delivery

    We present the result and answer questions. The document is yours.

FREQUENTLY ASKED QUESTIONS

What people usually ask us

Does the analysis include development?

No. It is a fixed engagement that ends with the delivery of the document. If you then want us to build it, the analysis is the basis of the proposal and is not repeated.

Can I use the document with another provider?

Yes. The document is yours and is written so any team can quote and build from it.

How long does it take?

It depends on the size of the project and the availability of the people to interview. We give you the timeline in the proposal, before starting.

LET'S TALK

Shall we look at it together?

Tell us where you are and we will suggest how to start. We reply within 24 working hours.

Tell us about your project

We reply within 24 working hours.

We only use technical cookies, which are needed for the website to work, and a preferences cookie to remember your language if you change it. We do not use analytics or advertising cookies. You can find the details in our Cookie Policy.