Business Analysis Services for requirements engineers can build against.
We provide business analysis services for product sponsors and process owners. We elicit requirements, model selected workflows and write specifications that engineering and QA can use to estimate, build and validate the agreed work.
- 120+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
Choose the first requirements scope
Commission focused discovery for the next scope decision, or agree continuing requirements support through delivery. We define the interviews and artifacts around that decision.
- Continuity when it serves deliveryAn embedded analyst clarifies requirements and updates the selected specification through agreed releases. Your product owner retains priority and approval authority unless you agree a different role.
- 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 selected features and acceptance. 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 analysis depth 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 fit a separately contracted 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 forSelected discovery, 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 selected 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 selected 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 clarification when needed. Our guide to SRS mistakes explains specification checks. |
| You end up owningThe selected artifacts 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 throughClarify the affected requirement
With one signal, review the selected feature or workflow and agree the acceptance it needs. We can work alongside your product owner on that focused analysis.
Talk it throughWorth 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 callCoordinate the requirements decisions
Three signals justify reviewing stakeholder expectations, process rules and system boundaries together. We define the selected models and specification, with a decision owner on your side to approve the scope.
Book a discovery callScope coordinated discovery and delivery support
With all four signals, agree the interviews, process models and specification for the selected workflow. An analyst can continue through delivery when that role is included. Most engagements start within two to four weeks.
Start with discovery04Capabilities
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, prototypingWe use selected 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-BeWe 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 criteriaWe write requirements engineers can build against in a software requirements specification (SRS). Selected user stories, 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, authorityWe identify the stakeholders with process knowledge, interests and approval authority. The selected register and communication plan define who contributes requirements, who reviews them and who decides when expectations differ.
- Non-functional requirements analysis
Non-functional and compliance requirements
GDPR, HIPAA, PCI-DSSWe specify selected performance, security, accessibility, observability and retention conditions as non-functional requirements. Your compliance owner supplies the applicable rules; we document agreed compliance requirements and how the team will review acceptance.
- Integration analysis
Systems and integration analysis
Which system owns which dataWe document the selected systems, data responsibilities and exchanges the solution needs. Your system owners confirm interfaces and business rules. Building the connectors is a separately agreed implementation responsibility.
- Cost-benefit analysis
Options, and the case for one of them
Option comparisonWe 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 forWe agree how the selected 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 an analysis engagement hands over
We agree the analysis artifacts and their acceptance around the selected software scope. The handover defines how your delivery team can use them.
- BuildableA specification engineers can build fromSelected functional 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 check and argue with
- YoursThe register, the models, the specification and the estimateSelected artifacts handed over under agreed access, use, IP and document-ownership terms
06Stack
The systems our requirements get built against
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.
Angular
.NET
Node JS
PostgreSQL
AWS
Shopify07Engagement
How you engage an analyst, 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 artifacts you need.
An analyst embedded in the team
Through deliveryAn 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 deliverableA defined analysis scope selects the interviews, models, specification and estimate assumptions required for your next decision. Artifact 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 analysisYour product owner retains priorities and approval. We take responsibility for the selected elicitation, process modeling or integration analysis, using your existing requirements as the starting point.
- Best when
- A selected flow or phase needs further analysis alongside your existing team
- You pay
- Billed hourly, quoted per project
- Typical start
- Two to four weeks
Use the existing specification for the next decision
We review the selected requirements against the systems and acceptance 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.
Logistics and transportation
Field operations where the requirement is scale rather than features: on a vehicle inspection platform the constraint we specified around was how quickly each new client could be brought into the operation databases and served.
Hospitality and leisure
Booking, membership and venue workflows with selected API, hardware and software requirements. A rental operator described those requirements being checked before agreeing a development phase.
E-commerce and retail
A European manufacturer of scented products selling B2B and B2C in seven EU countries. Its programme scope connected Shopify storefronts, Microsoft Dynamics ERP and custom middleware through current-state and target-state process models.
Commodity trading (CTRM/ETRM)
On a private B2B trading platform the requirement that mattered most was a rule rather than a feature: loop every negotiation, message and contract signature onto the marketplace so no deal can happen off it.
Accounting and financial advisory
We took over an unfinished bookkeeping automation where the accountancy logic the tool had to replicate is not easy to communicate remotely, so a team joining mid-build had to absorb it before extending anything.
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 artifacts needed for focused discovery or continuing analysis.
What happens after you contact us
- We reply within one business dayWe identify the process and specification information needed to scope the analysis.
- A call about your process and who has to agreeWhich decision the analysis supports, who knows the process and who approves the requirements.
- An agreed analysis scopeSelected interviews and artifacts, your inputs and approval roles, and the basis for the estimate.
- Choose the role and a start dateFocused discovery, targeted clarification or continuing analysis, agreed around 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.
- Intake and stakeholder mapYou provide the product or process objective and existing documents. We identify the selected stakeholders, their knowledge and decision authority, then agree the interviews, artifact depth and approval responsibilities.You getAn agreed analysis scope and, where selected, a stakeholder register and communication plan.
- 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 selected scope.
- Process modelingWe model the selected 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 getThe selected As-Is and To-Be models and agreed improvement decisions.
- Specification and estimateWe document selected 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.
- Validation through deliveryWhen continuing analysis is included, we clarify requirements, review agreed acceptance and update the selected 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
Communication with Artelogic is straightforward. They establish a clear understanding of our requirements and request additional details about tasks when needed. I find it amazing that they can finish before our deadlines. They deliver high-quality work, as well. Artelogic’s developers are the best we’ve collaborated with.
Artelogic anticipates our needs and meets them before we even identify them. My team lead wants to keep both of Artelogic’s developers on the project until the product’s release. We have a backlog of 40 big projects, so I only see Artelogic’s involvement increasing.
We scoped out the workflow for the platform. Using this foundation, Artelogic’s executing our requirements and developing the platform. Artelogic executed flawlessly according to our plan thus far. Their work ethic is impressive.
Artelogic invested time to understand our needs and has subsequently proposed appropriate solutions. In the end, the team’s quality deliverables have created value for cost. The EDI tool generates significant daily revenue and helps us solve order collection issues.
I’ve heard from several users that they find the site to be clearer in the message we’re trying to convey. I would say they were exceptional with communication; they clearly articulated where we were in the process and what the next steps were. Compared to my experience with other developers, I would say that this was a productive project.
11Case studies
Three engagements, from the scope up
Requirements work within commerce, food-production and trading programmes, including process models and development from an existing product requirements document. Earlier work was delivered under our former Artelogic brand; client quotations retain their original wording.
See all case studies
eCommerceEcommerce software development for JewelCandleJewelCandle, a mid-size European manufacturer of scented products, sells across seven EU countries (B2B and B2C) via online shops.10,000-plusProducts manufactured
FoodtechDigital Transformation in Food IndustryOur client is an innovation-oriented group of food companies based in Germany that produces and distributes a wide range of products for well-known retail businesses and food services.
TradingSoftware for trading with Smart contractsOur client, an experienced commodities trader, came to unicrew with a detailed PRD (Product Requirements Document) to develop the trading platform.
12Questions
About business analysis
Business analysis defines software scope and acceptance. Technology advisory informs technical decisions; automation implements the selected workflow.
A business analyst delivers the selected requirements and analysis artifacts your team needs to decide, estimate, build or validate software.
We agree the artifact depth 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; the handover identifies the delivery team using the artifacts and the agreed use and ownership terms.
We quote the agreed analysis scope around the interviews, systems and artifact depth 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 is agreed for the selected interviews, systems and depth of specification.
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 selected 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.
We confirm the assigned analyst's location and working overlap when we scope the engagement.
Remote interviews use video calls and shared documents, with the format and participants agreed for the selected requirements. 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 selected 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 selected artifact depth, 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 priority and sign-off roles 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 selected 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 selected 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 selected work.
The handover identifies open decisions, dependencies and estimate assumptions. If continuing analysis is included, the analyst clarifies requirements and updates the selected specification as changes are approved. Your product owner or sponsor retains priority and acceptance authority unless a different responsibility is explicitly agreed.