Skip to content

Business Analysis Services for requirements engineers can build against.

We provide business analysis services for product sponsors and process owners. We elicit requirements, model your workflows and write specifications that engineering and QA can estimate, build and validate against.

  • 150+Projects delivered across 12 countries since 2012
  • 5.0Unified rating across 61 client reviews on Clutch
  • ISO 27001Certified security practice, audited by Quay Audit UK
  • ISO 9001Certified quality management, audited by Quay Audit UK
  • PMPCertified project managers

01Overview

Define the requirements for your next decision

Commission focused discovery to define the next phase, or agree continuing requirements support through delivery. We plan the interviews and documentation around that decision.

  • Continuity when it serves deliveryAn embedded analyst clarifies requirements and updates the specification release by release. Your product owner retains authority over priorities and approvals.
  • Elicit the business rulesRequirements elicitation uses interviews, workshops and document analysis to establish what the system must do. You provide the process knowledge and decision owners who confirm those requirements.
  • Build on an existing specificationWe can review an existing product requirements document and clarify features and their acceptance criteria. A commodity trader's detailed document served as the starting point for further feature definition.
  • Direction, definition and implementationTechnology advisory informs platform and feasibility decisions. CTO consulting provides technical leadership. Automation implements the agreed workflow.

02Proof

Analysis within delivered software programmes

Assess the analyst's responsibility within the delivery programme, and read implementation results in the context of the whole build.

  • JewelCandle's product owner asked where we found the analystOn a team extension engagement, JewelCandle’s Head of IT told Clutch: "My product owner asked where we found one of Artelogic’s business analyst, calling him a superstar. If we could, we’d hire them ourselves." The client described usually working with three people: two senior developers and an experienced QC/BA embedded in its team.
    Three projectsthe programme scope: Shopify storefronts, Microsoft Dynamics ERP and custom middleware
  • The research came before the codeA software company in Munich brought the idea and we did the research for its recognition-tool build. The client later requested a BA role to discuss more complex projects in detail without involving the development team directly.
    2xdata sets processed per month after the operator-assisted recognition build, up from about 5,000 a month with two operators typing by hand
  • Analyst credentials and organizational auditWe have business analysts holding CBAP, AAC and PMP certifications. Our organizational security and quality management certifications are renewed through external audit; the engagement defines the assigned role and analysis outputs.
    ISO 27001:2022 and ISO 9001:2015, renewed through a multi-stage audit with Quay Audit UK, with analysts holding certifications including CBAP, AAC and PMP

03Compare

When does a business analyst fit the work?

Choose the depth of analysis around the decisions and requirements your delivery team needs. Your own analyst or product owner can manage that work; a BA-only consultancy can also prepare a separately commissioned specification. Continuing support is an agreed option.

A unicrew analyst in the teamunicrew Your own BA or product ownerIn-house Skip it and start buildingSkip
Best forDiscovery, process modeling or specification work, with optional requirements support during implementation. Best forA team whose analyst or product owner can document requirements and resolve the scope decisions. Best forA prototype or existing specification with sufficiently clear behavior, constraints and acceptance for the next build.
What it asks of youProcess documents, access to the right stakeholders and an owner who approves priorities and requirements. What it asks of youTime for elicitation and documentation, plus clear authority for approving the requirements. What it asks of youChecking assumptions and acceptance before development, and assigning responsibility for clarification when needed. Our guide to SRS mistakes explains specification checks.
You end up owningThe analysis documents, under agreed handover, use and ownership terms, with any continuing analyst role defined in scope. You end up owningYour requirements, priorities and responsibility for keeping the specification current. You end up owningThe implementation delivered against the existing scope, under its agreement, and decisions on subsequent changes.

Quick self-check

Tick what is true for you. The read-out updates as you go.

0 of 4 true

Your team already writes the scope

An existing specification may support the next build with focused clarification. We can scope a dedicated development team around it. Platform or feasibility decisions fit technology advisory, while technical leadership fits CTO consulting.

Talk it through

Clarify the affected requirement

With one signal, review that feature or workflow and agree its acceptance criteria. We can work alongside your product owner on that focused analysis.

Talk it through

Worth scoping as discovery

With two signals, discovery can establish the relevant process and requirements before the next estimate. We agree which stakeholders and systems to examine, using existing documentation where it serves the decision.

Book a discovery call

Coordinate the requirements decisions

Three signals justify reviewing stakeholder expectations, process rules and system boundaries together. We define the models and specification, with a decision owner on your side to approve the scope.

Book a discovery call

Scope coordinated discovery and delivery support

With all four signals, agree the interviews, process models and specification for the workflow. An analyst can continue through delivery when that role is included. Most engagements start within two to four weeks.

Start with discovery

04Capabilities

What our business analysts do

We select the analysis work around the decisions your specification must support, from stakeholder interviews to acceptance of the implemented solution.

  • Requirements elicitation

    Requirements elicitation

    Interviews, workshops, prototyping

    We use interviews, documents, workshops, observation or prototypes to establish the product's behavior and constraints. On an early-stage research SaaS, we collected core requirements from the main stakeholders before design.

  • Business process modeling

    Business process modeling

    BPMN, As-Is and To-Be

    We model the current process (As-Is) and agreed target process (To-Be) using BPMN, a notation for reviewing activities and responsibilities. On a seven-market e-commerce programme, current-state models informed the improvement plan.

  • Software requirements specification

    Requirements specification

    User stories with acceptance criteria

    We write requirements engineers can build against in a software requirements specification (SRS). User stories and functional and non-functional requirements carry agreed acceptance criteria. Your decision owners approve priorities, constraints and assumptions used in the estimate.

  • Stakeholder analysis

    Stakeholder mapping and alignment

    Interest, influence, authority

    We identify the stakeholders with process knowledge, interests and approval authority. The stakeholder register and communication plan define who contributes requirements, who reviews them and who decides when expectations differ.

  • Non-functional requirements analysis

    We specify performance, security, accessibility, observability and retention conditions as non-functional requirements. Your compliance owner supplies the applicable rules; we document the compliance requirements and how the team will review acceptance.

  • Integration analysis

    Systems and integration analysis

    Which system owns which data

    We document the systems, data responsibilities and exchanges the solution needs. Your system owners confirm interfaces and business rules, and our team can build the connectors.

  • Cost-benefit analysis

    We compare business options and their assumptions so your sponsor can choose the scope. Technical feasibility, stack and architecture recommendations belong in technology advisory when that additional work is needed.

  • Solution validation

    Solution validation

    Built against what was asked for

    We agree how the solution will be checked against approved requirements, and update the specification when changes are authorized. On one e-commerce programme our QA engineers developed the test plan and test cases.

05Trust

What you receive from an analysis engagement

We agree which analysis documents and acceptance criteria your software project needs. The handover defines how your delivery team can use them.

  • BuildableA specification engineers can build fromFunctional and non-functional requirements, with agreed acceptance criteria
  • Written downHow the work runs today, and what it becomesCurrent-state and target-state process models, in a form several departments can review and discuss
  • YoursThe register, the models, the specification and the estimateDocuments handed over under agreed access, use, IP and ownership terms

06Stack

The systems your requirements need to support

We examine requirements in the context of your existing business systems and interfaces. Technology choices and implementation remain separate decisions agreed with your technical owners.

FrontendWhat your users touch
BackendServices, APIs, and business logic
DataStorage, search, and data platforms
CloudWhere it runs, and what it costs
PlatformCommerce, CMS, and business platforms

07Engagement

How to work with our analysts, and how you pay

Choose a defined discovery output, continuing requirements support or focused analysis alongside your product owner. The role follows the decisions and documents you need.

  • An embedded analyst supports the agreed delivery scope, clarifying requirements and reviewing acceptance with your team. We define how the specification is maintained as priorities and requirements change.

    Best when
    Your programme needs continuing requirement clarification and acceptance support
    You pay
    Billed monthly, per team member
    Typical start
    Two to four weeks
  • A scoped discovery

    Named deliverable

    We define the analysis scope around the interviews, models, specification and estimate assumptions required for your next decision. Document handover and use are agreed; implementation is a separate purchase.

    Best when
    You need a defined specification and estimate assumptions for an investment decision
    You pay
    Outcome based, quoted per project
    Typical start
    Two to four weeks
  • An analyst alongside your own team

    Targeted analysis

    Your product owner retains authority over priorities and approvals. We take responsibility for the elicitation, process modeling or integration analysis you need, using your existing requirements as the starting point.

    Best when
    A specific flow or phase needs further analysis alongside your existing team
    You pay
    Billed hourly, quoted per project
    Typical start
    Two to four weeks
You already have a specification

Use the existing specification for the next decision

We review the requirements against the systems and acceptance criteria they describe, then document the clarifications needed. You can commission that analysis independently, with no minimum engagement period. For an implementation needing recovery, we scope project rescue.

08Industries

Industries our analysts work in

We specify requirements around the records, activities and constraints of the operation, from vehicle inspections to commerce and accounting workflows.

Deepest expertise

Logistics and transportation

Field operations where scale matters more than features: on a vehicle inspection platform, we specified how quickly each new client could be onboarded into the operational databases.

Deepest expertise

Hospitality and leisure

Booking, membership and venue workflows have specific API, hardware and software requirements. A rental operator described how those requirements were checked before agreeing a development phase.

E-commerce and retail

A European manufacturer of scented products sells B2B and B2C in seven EU countries. Its programme connected Shopify storefronts, Microsoft Dynamics ERP and custom middleware, with current-state and target-state process models informing the work.

Commodity trading (CTRM/ETRM)

On a private B2B trading platform, the key requirement was to keep every negotiation, message and contract signature on the marketplace so no deal could happen outside it.

Accounting and financial advisory

We took over an unfinished bookkeeping automation project whose tool had to replicate accountancy logic. The client's head of product said our team "learned quickly" and reported "no situations of the system doing the wrong thing."

Automotive

Each car brand carries its own set of requirements and specifications, so on the same inspection platform the system had to be adjustable per client, down to adding new car characteristics for a new customer.

Define the requirements for your next software decision

Bring the process or product you want to develop and the documents you already use. We identify the decisions, stakeholders and documents needed for focused discovery or continuing analysis.

Let's talk

What happens after you contact us

  1. We reply within one business dayWe identify the process and specification information needed to scope the analysis.
  2. A call about your process and who has to agreeWhich decision the analysis supports, who knows the process and who approves the requirements.
  3. An agreed analysis scopeThe interviews and documents, your inputs and approval roles, and the basis for the estimate.
  4. Choose the role and a start dateFocused discovery, targeted clarification or continuing analysis, whichever fits your requirements. Most engagements start within two to four weeks.

09Delivery

How a business analysis engagement runs

Analysis follows the approval decisions behind your software scope. We agree who supplies process knowledge, who confirms requirements and who accepts changes through delivery.

  1. Intake and stakeholder mapYou provide the product or process objective and existing documents. We identify the stakeholders, their knowledge and decision authority, then agree the interviews, level of documentation and approval responsibilities.You getAn agreed analysis scope and, where needed, a stakeholder register and communication plan.
  2. ElicitationWe use the agreed interviews, workshops, documents and observation to establish behavior and constraints. You provide access to the people doing the work and the relevant system information. Your decision owners resolve conflicting expectations.You getDocumented requirements and open questions for the scope.
  3. Process modelingWe model the current and target workflows and document changes to activities and responsibilities. Your process owners confirm how the work runs and approve the proposed target state before its requirements are used for implementation.You getAs-Is and To-Be models and agreed improvement decisions.
  4. Specification and estimateWe document functional and non-functional requirements with acceptance criteria. Your sponsor approves priorities and scope; engineering contributes the technical assumptions needed for an estimate. Outstanding decisions and dependencies remain explicit.You getThe agreed specification and scope boundary, with estimate assumptions where estimation is included.
  5. Validation through deliveryWhen continuing analysis is included, we clarify requirements, review acceptance and update the specification. You nominate the people who accept the delivered behavior and authorize changes. Handover and further support follow the agreed role.You getAcceptance findings and authorized specification updates for the agreed delivery scope.

10Client voices

Our clients say

See our client reviews
5.0 unified ratingacross 61 verified client reviewsRead them on Clutch

12Questions

About business analysis

Business analysis defines software scope and acceptance. Technology advisory informs technical decisions; automation implements the chosen workflow.

A business analyst delivers the requirements and analysis documents your team needs to decide, estimate, build or validate software.

We agree the documents and level of detail in scope: a requirements specification, process models, stakeholder register, option comparison or acceptance criteria. Functional and non-functional requirements define behavior and operating constraints. Your decision owners approve priorities and acceptance criteria; the handover identifies the delivery team using the documents and the agreed use and ownership terms.

We quote the agreed analysis scope based on the interviews, systems and level of documentation it requires.

Existing documentation, stakeholder access and the requirements to be examined shape the estimate. The engagement determines billing:

  • Time and materials is billed hourly and quoted per project.
  • Fixed price is outcome based and quoted per project.
  • Team extension is billed monthly per team member.

There is no minimum engagement period. Implementation is a separate scope decision.

The analysis schedule follows the interviews, systems and depth of specification in scope.

Your stakeholder availability, existing documents and outstanding decisions affect that schedule. Focused discovery can have a defined handover; an embedded analyst can support requirements throughout the agreed delivery scope. Most engagements start within two to four weeks. That start window is separate from the duration of the analysis.

Yes. Systems and integration analysis can specify the interfaces, records, ownership rules and exchanges your solution needs.

Your system owners confirm those rules and available interfaces. A seven-market e-commerce programme covered Shopify storefronts, Microsoft Dynamics ERP and custom middleware. The ERP was planned as the source of truth for products and stock. Specifying those responsibilities and implementing the connections are separately agreed work.

Dedicated analysis fits when the next software decision needs coordinated requirement clarification, process models or acceptance definition.

A focused scope can address the affected workflow. An established specification can support a dedicated development team with clarification alongside your product owner, without restarting the analysis.

For broader product definition, we scope product design and development. A design sprint can fit when a prototype will help users and stakeholders evaluate the proposed behavior.

Our analysts are part of our in-house team, based in Ukraine, Poland, Estonia and the UK. We confirm the assigned analyst's location and working-hours overlap when we scope the engagement.

Remote interviews use video calls and shared documents, with the format and participants agreed for the requirements in scope. If the process needs observation, we plan that with the department responsible. Document access and any workshop recording are agreed as part of the work.

We agree which documents and data the analysis needs, who can access them and the terms for their use and handover.

We sign an NDA before access. Fixed-scope assessments use read-only, least-privilege access agreed with your technical contact; embedded analysis and implementation permissions are agreed separately. unicrew holds ISO 27001:2022 and ISO 9001:2015 certifications, renewed through a multi-stage audit with Quay Audit UK. The certifications cover our organizational management systems.

Compare the level of documentation, decision responsibilities, delivery continuity and relevant credentials.

unicrew has 100+ senior in-house engineers across six countries. For analysis alongside a unicrew build, we agree the specification's handover with the delivery team. We define the work before the engagement:

  • The specification scope identifies requirements and acceptance criteria for engineering and QA.
  • Your sponsor's roles in setting priorities and signing off requirements are explicit, alongside the inputs needed from stakeholders.
  • Any continuing analyst role, specification updates and handover terms are agreed in scope.
  • We have analysts holding certifications including CBAP, AAC and PMP. Our organizational ISO 27001:2022 and ISO 9001:2015 certifications were audited by Quay Audit UK.

Business analysis defines software behavior, process rules and acceptance; technology advisory informs technical feasibility, platform and architecture decisions.

The analyst documents what users and stakeholders need. Technical owners review implementation choices, while your sponsor approves priorities and investment. Both disciplines can be included where a programme needs requirements and technical recommendations, with their responsibilities agreed separately.

Business analysis documents the process and requirements; business process automation implements software to carry out the agreed workflow.

Analysis can produce current-state and target-state models and acceptance criteria. The automation scope then defines what the software executes and what remains a human decision. Existing process documentation can supply the starting point when it already supports those decisions.

Engineering and QA use the agreed specification and acceptance criteria to estimate, build and validate the work.

The handover identifies open decisions, dependencies and estimate assumptions. If continuing analysis is included, the analyst clarifies requirements and updates the specification as changes are approved. Your product owner or sponsor keeps priority and acceptance authority.

Thank you

Thanks for your message. We will get in touch with you shortly.

Book a call