Leasing a business analyst through 360 Soft gives you a specialist who turns business needs into clear, testable requirements, so that developers build the right thing the first time. The analyst works under a service agreement with 360 Soft, joins your team remotely, on-site or in a hybrid model, and works in English with your business units, product owners and developers. On this page you will find the scope of the role, seniority levels, a techniques and tools matrix, how we assess candidates, KPIs and the factors that shape the cost. This page is part of our IT staff leasing services.
Why companies need a business analyst
Most failed software projects do not fail because of code. They fail because the requirement was vague, the edge cases were never discussed, or two departments meant different things by the same word. A business analyst closes that gap. Typical reasons to bring one in:
- A new system (ERP, CRM, core banking, e-commerce, mobile app) is being selected or built and the requirements are scattered across emails and meetings.
- Developers keep asking the same questions and rework is eating the sprint capacity.
- The Product Owner has too little time to write and refine user stories.
- A legacy system must be replaced and nobody has documented how it really works.
- A process must change for regulatory reasons and the impact on systems must be mapped.
- An outsourced or nearshore development team needs one person who translates between the business and the developers.
Scope of the business analyst role
| Area | Typical tasks |
|---|---|
| Discovery | Stakeholder interviews, workshops, current-state (as-is) process mapping, problem definition |
| Requirements | Business, functional and non-functional requirements, user stories with acceptance criteria, use cases |
| Process design | To-be processes in BPMN, gap analysis, impact analysis |
| Data and integration | Data mapping, API and interface specifications with the technical team, report definitions |
| Delivery support | Backlog refinement, answering developer questions, supporting UAT and test scenarios |
| Change and adoption | Training material, release notes, feedback loops after go-live |
Seniority levels and responsibilities
| Level | Experience | What you can expect |
|---|---|---|
| Junior / mid BA | 2–4 years | Writes user stories and specifications for a defined area under guidance |
| Senior BA | 5–8 years | Leads discovery and workshops, owns requirements for a product or module, challenges assumptions |
| Lead BA / business architect | 8+ years | Shapes the solution across several systems, sets BA standards, works with executives on business cases |
Techniques, tools and skills matrix
| Area | Examples |
|---|---|
| Techniques | Interviews, workshops, MoSCoW prioritisation, user story mapping, BPMN 2.0, UML, use cases, event storming |
| Documentation and backlog | Jira, Azure DevOps, Confluence, Notion, SharePoint |
| Modelling and design | Visio, draw.io, Lucidchart, Miro, Figma (for wireframes), Camunda Modeler |
| Data | SQL for analysis, Excel, Power BI or Tableau for prototyping reports |
| Certifications (where held) | IIBA ECBA/CCBA/CBAP, PMI-PBA, PSPO, IREB CPRE |
| Domains | Banking and payments, insurance, retail and e-commerce, telecom, logistics, public sector |
Domain knowledge often matters more than tools. A BA who already understands payments or insurance products needs far less ramp-up time, so we match on domain first.
How we assess business analyst candidates
- Requirements exercise: the candidate receives a short, deliberately vague request and turns it into user stories with acceptance criteria.
- Process mapping: they model a simple process in BPMN and point out gaps or exceptions.
- Workshop role-play: how they handle two stakeholders who want conflicting things.
- Sample review: anonymised specifications or backlogs from previous work, where available.
- Communication check: written English quality matters for a BA, so we review their writing as well as speaking.
- Reference check: with previous managers or clients, where the candidate allows it.
You interview the shortlist and make the final decision.
Lease or hire permanently
Leasing fits when analysis capacity is needed for a project or a peak period, when you want to start within weeks, or when you need a domain specialist you cannot find locally. A permanent hire suits a long-term product role where you have time to recruit. Leasing also lets you test the role before committing to a permanent headcount.
Working models
- Remote: the specialist works from Türkiye inside your tools, with agreed overlap hours for EU, UK or Gulf time zones.
- On-site: at your office in Istanbul, or travelling for workshops, kick-offs and critical phases.
- Hybrid: mostly remote with regular on-site days.
- Delivery models: a single embedded analyst in your product team, or a BA working alongside a 360 Soft development team in an outsourced model.
Onboarding process and typical timelines
| Step | What happens | Typical duration |
|---|---|---|
| 1. Brief | We agree the role, skills, seniority, language and working model | 1–2 days |
| 2. Shortlist | We present tested candidates with short profiles | 3–7 days |
| 3. Interviews | You interview and choose | 2–5 days |
| 4. Contract and start | Service agreement, NDA, access set-up, kick-off | Typical start in 1–2 weeks overall |
| 5. First 30 days | Stakeholder map, review of existing documentation, first refined backlog or specification | First month |
KPIs for business analysts
| KPI | What it shows |
|---|---|
| Requirement-related defects | Bugs traced back to missing or unclear requirements |
| Rework rate | Stories reopened or rebuilt after review |
| Backlog readiness | Number of sprints of refined, ready stories ahead of the team |
| Clarification cycle time | How quickly developer questions are answered |
| UAT pass rate | Share of features accepted by users at the first attempt |
| Stakeholder satisfaction | Short periodic survey of business owners |
Factors that affect the price
We do not publish prices because every engagement is scoped individually. The main factors are:
| Factor | Effect |
|---|---|
| Seniority | Lead BAs and business architects cost more than mid-level analysts |
| Domain expertise | Banking, insurance or regulated-sector knowledge |
| Language | Fluent English or additional languages such as German or Arabic |
| Working model | On-site work and travel add cost compared with remote |
| Duration and allocation | Full-time or part-time; longer engagements are usually priced more favourably |
| Working hours | Overlap with distant time zones or 7/24 shift coverage |
Permanent analyst, freelancer and leasing compared
| Criterion | Permanent hire | Freelancer | Leased via 360 Soft |
|---|---|---|---|
| Time to start | Often 2–4 months | Fast, availability varies | Typically 1–2 weeks |
| Continuity | High | Risk of leaving mid-project | Replacement process if the fit is not right |
| Employer obligations | On you | Contract risk depends on your country | With 360 Soft under Turkish labour law |
| Scaling | Slow | One person | From 1 to 200+ people |
| Control over daily work | Full | Limited | You direct the work; we handle employment |
Risks and how they are managed
| Risk | Mitigation |
|---|---|
| The analyst lacks domain knowledge | Domain-matched shortlist and access to subject-matter experts in the first weeks |
| Documents nobody reads | Agree the format with the team: lean user stories over long documents where it fits |
| Scope creep through requirements | Clear prioritisation and a change process agreed with the Product Owner |
| Knowledge leaves with the person | All artefacts kept in your tools, and a handover plan |
| Poor fit with the team | You choose; replacement process if it still does not work |
Confidentiality, data protection and IP
The business analyst works under a B2B service agreement between your company and 360 Soft; there is no employment relationship between you and the specialist. The standard package includes a mutual NDA, an IP assignment clause under which all work product, documentation and code created for you belongs to you, and written access rules for your systems.
- EU/EEA buyers: a GDPR Data Processing Agreement (Art. 28) with Standard Contractual Clauses for transfers to Türkiye.
- UK buyers: the UK International Data Transfer Agreement (IDTA) or the UK Addendum to the SCCs.
- Türkiye: the team operates under KVKK (Law No. 6698), the Turkish personal data protection law.
- Access hygiene: named accounts, least-privilege access, MFA, your VPN or VDI where required, and access revoked on the last day.
Legal note
The specialist is employed by 360 Soft under Turkish labour law; payroll, social security and statutory obligations remain with us. This page is general information, not legal advice. Sector rules in Türkiye (for example BDDK for banking or SPK for capital markets) apply to work done there, and the local rules of your own country also apply; please have the agreement reviewed by your legal counsel.
Checklist for choosing a business analyst
- Which product, process or system will the analyst work on?
- Which domain knowledge is essential, and which can be learned?
- Do you need user stories, formal specifications, process models or all three?
- Who is the decision maker for requirements?
- Which tools must the analyst use from day one?
- What language and overlap hours do stakeholders need?
- How will you measure success after 30 and 90 days?
Example use
Illustrative scenario: an insurance company in the Gulf is building a customer self-service portal with a nearshore development team. Requirements exist only as slide decks. A senior business analyst joins remotely, runs workshops with claims and policy teams, maps the main processes in BPMN, and builds a prioritised backlog with acceptance criteria two sprints ahead of the developers. This is an example of how the role can be used, not a report of a specific client result.
Frequently asked questions
What is the difference between a business analyst and a Product Owner?
The Product Owner decides what gets built and in which order. The business analyst helps discover and describe the requirements in detail. In smaller teams one person may do both; in larger ones they work together.
Does the business analyst need technical skills?
Not coding, but a good BA understands APIs, data models and system constraints well enough to talk to developers and write realistic specifications. SQL skills are a plus.
Can the analyst document an existing legacy system?
Yes. Reverse-engineering current processes and system behaviour is a common task before a replacement project.
Do you provide analysts with banking or insurance experience?
Yes, we can match on domain. Tell us the domain and the systems involved in the brief.
Which language do your analysts work in?
English is standard for international clients. German or Arabic can be requested and affects availability.
How quickly can a business analyst start?
The typical start is within 1–2 weeks after the brief.
Can the analyst work part-time?
Yes, if the workload allows it, for example for a smaller product or a support role after go-live.
Do I interview the candidates myself?
Yes. We pre-assess candidates and you interview the shortlist and decide.
What happens if the analyst is not the right fit?
We start the replacement process and arrange a handover so that requirements work continues.
Who owns the documents the analyst produces?
You do. The service agreement includes an IP assignment clause covering all work product.
Talk to us about your team
Tell us the product or process, the domain, the number of analysts and your target start date. We reply with candidate profiles and an indicative timeline. Call +90 850 335 10 87, message us on WhatsApp, email info@360-soft.com or use our contact page.
360 Soft Marketing Yazılım ve Danışmanlık Ltd. Şti. · Nidakule Ataşehir Batı, Barbaros Mah. Begonya Sk. No:1 D:2, 34746 Ataşehir/İstanbul, Türkiye.
Related pages
- IT staff leasing hub
- Project manager and Scrum Master leasing
- Data engineer leasing
- Hire developers in Türkiye
- Türkçe: Türkçe sürüm
Related services
- Cloud Architect LeasingLease a senior AWS, Azure or Google Cloud architect from Istanbul for migration, landing zones and FinOps…
- Cyber Security Specialist LeasingLease cyber security specialists: SOC analysts, vulnerability management, security engineers, GRC. Remote or…
- Data Engineer and Data Analyst LeasingLease data engineers and analysts: ETL/ELT, Snowflake, Databricks, BigQuery, dbt, Power BI. Remote or…
- Database Administrator (DBA) LeasingLease an Oracle, SQL Server, PostgreSQL or MySQL DBA from Istanbul. Remote or on-site, 7/24 coverage…
- Help Desk and IT Support Specialist LeasingLease help desk and IT support specialists for L1–L3, remote or on-site, business hours or 7/24. From 1 to…
- Project Manager and Scrum Master LeasingLease an experienced project manager or Scrum Master from Istanbul. Agile, PRINCE2 or hybrid, remote or…
