Hire business analysts
Business analysts for software projects: discovery, requirements, user stories, process maps and acceptance criteria that engineers can build from and testers can check, for product teams and for companies replacing or connecting business systems.
What our business analysts do
Discovery workshops
Structured sessions with the people who do the work today, ending in a written summary of goals, constraints and open questions that every participant has read and corrected.
User stories and acceptance criteria
Stories small enough to finish in a sprint, each with acceptance criteria in Given, When, Then form that a QA engineer can turn straight into a test.
Process mapping
Current and future processes drawn in BPMN 2.0, so the steps that software will automate, change or remove are agreed before anyone builds them.
Data and integration analysis
Field-level mappings between systems, the rule for every transformation and an owner for every record, written down before an integration or a data migration is built.
Prototypes with designers
Wireframes and clickable Figma prototypes made with a UI designer, so a flow is tested with its users before it costs engineering time.
Traceability and sign-off
Each requirement linked to the stories that deliver it and the tests that prove it, so a change shows what else moves and nothing is signed off untested.
Hire business analysts
Full time in your team
Business analysts who work your hours in your tools and meetings and report to your lead, with the Ukrainian contract, payroll and leave on our side.
Part time or fractional
Business analysts for a set number of days a week, when the work is real but not yet a full-time role.
For a project or a launch
Business analysts for a defined stretch of work, from the first week to the handover, with the end date agreed up front.
The dedicated team page explains how specialists join your team, and the outsourcing page covers project delivery, take-overs and how we charge.
Who our business analysts work with
Product owners and stakeholders
Goals, priorities and sign-off
Engineers and technical leads
Feasibility and estimates
QA engineers
Tests built from the acceptance criteria
UI and UX designers
Flows and prototypes in Figma
Business analyst or product manager
A business analyst works out what the software must do and writes it down precisely enough to build and test. A product manager decides what is worth building and in which order. On a project with a fixed goal, such as replacing a system or connecting two, the business analyst is usually the missing role; on a product competing for users, it is the product manager.
Our business analysts write in your tracker and your wiki, whether that is Jira and Confluence, Azure DevOps or Notion, so the requirements stay with your project after the engagement ends.
Other roles we staff
Project managers
Project management for software delivery: IT project and delivery managers who own plans, scope, risks, budgets and weekly reporting, full time in your team, part time or for a single project.
Product managers
Product management for software products: product managers and product owners for discovery, roadmaps, backlogs and product metrics, full time in your team, a few days a week or for a launch.
Scrum masters
Scrum masters and agile coaching for software teams: Scrum and Kanban, flow metrics, impediments removed and retrospectives that change something, full time in your team, part time or for a set period.
Technical writers
Technical writing services: API documentation from OpenAPI, developer guides, help centres, runbooks and release notes written as docs as code, by technical writers in your team or for a project.
Technical support
Technical support services for software products: first and second line support engineers in your help desk, under your brand and in your customers' hours, full time, part time or for a launch.
IT recruitment
IT recruitment services for companies building their own teams: role briefs, sourcing, screening and technical interviews by working engineers, from IT recruiters in your team or for a hiring push.
Customer success
Customer success management for SaaS and subscription products: customer success managers for onboarding, adoption, health scores, QBRs and renewals, full time in your team, part time or for a launch.
Questions about hiring business analysts
Does a business analyst need to know our industry?
Domain knowledge shortens the first weeks, and we look for it when we propose someone. The method matters more: asking the people who do the work, writing down what they say, and checking it back with them before it becomes a requirement.
Can a business analyst help us replace an old system?
Yes, and that is where the role pays back most. The analyst documents what the old system really does, including the rules nobody wrote down, so the replacement is not specified from memory. It is the same discipline our take-overs start with: a read-only review and a written list of risks before anything changes.
How quickly can business analysts start?
When the right business analyst is available, the start is gated only by your interview and the NDA and IP assignment. Otherwise we run a search, which typically produces candidate profiles within two to three weeks, and nobody starts until you have said yes.
How do we hire business analysts through BigTree108?
Tell us the work, the seniority and the hours you need. We propose one or two people with their profiles, you interview them the way you would interview your own hire, and you sign one agreement with BIG TREE 108 LLC and receive one invoice a month.
Who owns the work they produce?
You do. Every specialist has a signed contract with BigTree108 that assigns all work product to the company, and our agreement with you assigns it onward. Code, designs and documents are delivered into your own repositories and tools, not kept where only we can change them.
Need requirements your team can build from?
Tell us the project and where the requirements stand today. You get an answer within one business day: candidate profiles or a plan for discovery.