Business Analyst

A signed SOW is only as good as what happens to it next. This role exists to be the critical bridge between Sales, Project Intake, and Delivery Execution — making sure every signed project enters development with clarity, completeness, and functional accuracy, instead of ambiguity that surfaces three weeks into a build.
You’ll convert signed SOWs, discovery notes, and client requirements into structured, developer-ready documentation. Your work directly protects delivery efficiency, quality, and client satisfaction by catching gaps before development begins, not after.
This role is for someone who enjoys:
Turning ambiguous requirements into precise, structured documentation
Catching gaps and inconsistencies before they become delivery problems
Working at the intersection of Sales, PMs, Developers, and QA
Building reusable systems and templates rather than solving the same problem repeatedly
If you’re someone who takes real satisfaction in a requirement document that leaves zero room for misinterpretation, this role will put that skill to constant use.
What you’ll really be doing
1. Project Intake & Transition
Review signed SOWs, proposals, discovery notes, and transcripts
Participate in internal kick-off sessions to understand client priorities and technical constraints
Identify gaps, ambiguities, or missing inputs before development begins
Ensure complete transition from Sales to Delivery with zero requirement blind spots
2. Requirement Documentation
Translate business requirements into Functional Requirement Documents (FRDs) and detailed User Stories
Break down modules and features into data fields, validations, workflows, interactions, and conditional logic
Define dynamic content behavior, click actions, role-based access views, and system logic
Ensure documentation is structured, version-controlled, and delivery-ready
3. Internal Task Structuring & Execution Alignment
Collaborate with Project Managers to convert requirements into structured development tasks (ClickUp, Jira, etc.)
Identify task dependencies and logical execution sequences
Support QA teams with initial test case outlines derived from business rules and acceptance criteria
4. Client Clarifications & Change Management
Track and document clarification requests during execution
Support PMs and Account Managers in evaluating scope deviations and change requests
Maintain version-controlled documentation with client confirmations and change logs
5. Quality & UAT Support
Assist PMs in validating completed work against functional documentation before client delivery
Participate in internal UAT cycles to ensure alignment between build and documented requirements
Reduce last-minute surprises during client reviews
6. Documentation Governance & Hygiene
Maintain centralized repositories of requirement documents and change logs
Ensure consistent formatting, naming conventions, and version control standards
Regularly clean up outdated or deprecated documentation references
7. Proactive Risk Identification
Identify risks, inconsistencies, and vague requirements early in the process
Escalate potential delivery blockers before development begins
Flag redundant or unclear SOW elements that may lead to misinterpretation
8. Cross-Department Collaboration
Work closely with UI/UX designers to ensure designs align with documented functionality
Annotate design files and provide developer-facing logic notes
Clarify workflow expectations and display conditions across teams
9. Process & Template Improvement
Refine internal templates for FRDs, change tracking, and requirement mapping
Recommend process improvements to reduce friction during handoffs
Improve intake efficiency through structured documentation patterns
10. Knowledge Sharing & Reusability
Document recurring modules, platform constraints, and reusable logic patterns
Build and maintain an internal knowledge base for delivery reference
Support onboarding by providing structured background documentation
Who will thrive in this role
You catch ambiguity and gaps before anyone else notices them
You write documentation precisely enough that a developer never has to guess
You move comfortably between Sales, PMs, Developers, and QA without losing context
You maintain documentation discipline even when things get busy
You think in reusable systems, not one-off fixes
Qualifications & Skills
Experience
5 years of experience as a Business Analyst in a digital agency, web development, or software delivery environment
Must Have Skills
Strong experience creating FRDs, user stories, process flows, and QA outlines
Ability to convert business requirements into clear, structured, developer-ready documentation
Strong analytical thinking and logical reasoning skills
Excellent written and verbal communication abilities
Exceptional attention to detail and documentation discipline
Strong understanding of website or application development lifecycles
Tools & Platforms
Figma, Jira, ClickUp, Miro, Lucidchart, Confluence
Google Workspace
Nice to Have
Experience working with US-based agencies or white-label service models
Familiarity with SOWs, BRDs, technical specifications, and structured discovery documentation
Understanding of WordPress, Shopify, custom PHP/JS builds, and API integrations
Ability to annotate UI/UX designs and suggest usability improvements
Knowledge of risk management, prioritization frameworks, and delivery dependency mapping
What this role offers
A high-impact role sitting at the center of Sales, Delivery, and Client Success
Ownership of the documentation that determines how smoothly every project runs
Exposure to a wide variety of client projects and platforms
Room to shape and improve internal documentation standards and templates

Work arrangement
No