Senior Business Analyst (Contract)

Join Winthrop Wealth as a contract Senior Business Process Analyst reporting to the CTO. In 2026, Winthrop Wealth is focused on Build to Scale: making the operational and technology investments that allow a growing advisory firm to deliver consistent, high-quality client service without adding complexity. You will be central to that effort.

Winthrop Wealth has never had a dedicated business analyst. Individual departments have owned their own processes and standard operating procedures, and the consistency of that documentation varies widely. Your job is to bridge the gap between business teams and the technology team by formalizing processes and requirements that exist in practice but have not been consistently documented, translating business needs into specifications our technology team can execute, and producing the operating procedures on the other side. Your primary output is documentation that drives decisions and unblocks implementation: process maps, gap analyses, sprint-ready user stories, and standard operating procedures.

This is a milestone-based engagement. If your Month 1 and Month 2 deliverables are usable by the technical team, the engagement extends. If they are not, we will know within 60 days and adjust. The firm is making a multi-year technology investment, and your work in the first three months produces the evidence base that justifies continued investment.

Your First Engagement: Service Orchestration

Your initial responsibilities will center on the firm's service orchestration, which directs the scope, methodology, and timing of Winthrop Wealth's continued delivery of service packages to each client household. Service date management (SDM) is a pivotal component of these packages, defining the schedule for the provision of various service elements to ensure the consistent quality of Winthrop Wealth’s services. You will be engaged in two simultaneous workstreams.

Workstream 1: SDM Documentation and Requirements Support

There is a Salesforce implementation already in progress with its own history and momentum. A UAT Lead is actively testing. You are not starting from zero. You are walking into a moving project that has gaps in documentation, requirements formalization, and stakeholder alignment. Your job is to support the existing UAT structure by filling those gaps: documenting what actually exists, refining informal requirements into formal specifications, and producing output, such as artifacts and reuseable templates, that advances the project toward production readiness. Teams across the firm have created workarounds wherever official processes did not keep up. You will need to navigate competing priorities, separate real needs from positional preferences, and deliver clear and concise specifications the technology team can execute quickly.

Workstream 2: Client Review Process (A Vital Service Element)

You will lead the firm through a structured effort to capture, synthesize, and integrate existing departmental workflows into a single documented standard for one of its most important client-facing service elements: the Client Review. This is the process by which Winthrop Wealth prepares for, conducts, and follows through on periodic reviews with each client household. It is a complex cross-departmental workflow that spans Advisory, Client Service, Operations, Financial Planning, Portfolio Management, and Compliance. Each of these teams knows their own piece well. What has never existed is a single document that captures the full arc across all six departments as one integrated workflow.

You will work with internal stakeholders to capture the entire process from data gathering and preparation through client impact: how review materials are assembled, how advisors prepare, how the meeting is conducted, what happens afterward, and how follow-through is tracked and completed. You are not uncovering hidden processes. You are sitting with experienced professionals who know exactly what they do, capturing it, and then doing the harder work of connecting the seams between departments: where does Client Service’s output become Portfolio Management’s input, where does the advisor’s preparation depend on something Operations produced, where does Compliance need visibility that nobody is currently providing.

The broad strokes are largely the same from advisor to advisor, but not exactly the same, and some of that variation may be perfectly fine. Your job is to drive toward standardization of substance: the steps, decisions, handoffs, and quality checkpoints that should be consistent across every client review. How an advisor conducts the performative part of a client meeting is their craft. What happens before and after that meeting, and what the firm can count on being done the same way every time, is yours to document and standardize.

This requires more than transcription. You must be curious. You need to be critical of existing processes, not adversarial, but genuinely interrogative. At each stage, you should be driving toward the core function: why does this step exist, why is it done this way, and should it remain this way or not? Some of what you find will be well-reasoned and worth preserving. Some will be legacy habit that no one has questioned. Your documentation should make the difference visible and present the case either way.

Your output needs to be thorough enough to serve two purposes. First, it establishes a unified, documented standard for how client reviews work at Winthrop Wealth, surfacing meaningful differences across teams and resolving the ones that matter. Second, it creates the foundation for identifying where AI can be injected into the workflow to elevate client outcomes. You are not building the AI solutions. You are producing the documentation that makes intelligent automation ai-enabled workflows possible, because you cannot improve a process you have not formally captured.

Engagement Milestones

This engagement has concrete milestones. Renewal depends on hitting them.

Month 1 - Current-State Documentation

• SDM: Process maps and gap analysis supporting the existing UAT structure, validated by department leads. Data flow documentation feeding the firm’s compliance systems inventory.
• Client Review: Stakeholder interviews completed across Advisory, Client Service, Operations, Financial Planning, Portfolio Management, and Compliance. Integration plan documented with scope, dependencies, and sequencing for synthesizing departmental workflows into a single end-to-end standard.

Month 2 - Specifications and Standardization

• SDM: Sprint-ready acceptance criteria and user stories for the Salesforce implementation, accepted by the development team. Specifications structured so that any technical resource can execute without a follow-up meeting to clarify intent.
• Client Review: Documented end-to-end process with variance analysis across advisory teams, standardization recommendations for substantive steps and handoffs, and initial identification of friction points and gaps.

Month 3 - Integrated Roadmap

Combined prioritized roadmap pulling from both workstreams: sequenced implementation plan for SDM and Client Review standardization, with AI-readiness recommendations identifying where automation could elevate client outcomes. Presented to the CTO and Director of Operations as the basis for the next phase of investment.

Beyond the Initial Engagement

For a contractor who delivers strong Month 1 to 3 output, the engagement extends into execution support. That phase includes SOP creation as new workflows go live, coordination with the UAT lead during user acceptance testing, and knowledge transfer structured so a second analyst can pick up workstreams without re-interviewing stakeholders. There is also a broader set of firm workflows beyond the Service Delivery Model that will need the same treatment. The scope of continued work depends on the quality of the initial engagement and the firm’s evolving priorities, but the runway is real for someone who proves they can do this work.

Responsibilities

As our Senior Business Process Analyst, you will:

Formalize current-state documentation across the firm by:

• Mapping current-state workflows across Advisory, Client Service, Operations, Compliance, Portfolio Management, Financial Planning, and Information Technology
• Conducting stakeholder interviews across all departments to understand how work gets done in practice, not how people think it gets done
• Identifying where teams have built workarounds, where information gaps exist between systems, and where undocumented processes have become the de facto standard
• Synthesizing individual departmental workflows into integrated, end-to-end process documentation, particularly where handoffs between teams are undocumented or informal
• Producing process maps and gap analyses scaled to the decision they support, with enough specificity that your output serves both the technology team and the Compliance team
• Tracing upstream and downstream impacts when a process change in one area affects adjacent workflows
• Identifying viable KPIs for each documented workflow and establishing baseline measurements, so the firm has a quantitative foundation for evaluating the ROI of any proposed process changes or technology investments.

Refine business needs into sprint-ready specifications by:

• Writing user stories or acceptance criteria that the development team can execute in sprint cycles without scheduling a follow-up meeting to clarify what was meant
• Distinguishing between what stakeholders say they want and what the business actually needs, documenting both, and reconciling the difference with the stakeholder before handing off
• Prioritizing requirements by business impact, regulatory obligation, security implications, and implementation complexity
• Maintaining requirements traceability from discovery through testing, confirming delivered solutions resolve each defined requirement
• Structuring all specifications so that any technical resource can pick them up and execute without having been in the room during discovery

Establish a prioritized implementation roadmap by:

• Facilitating definition of target-state processes based on your current-state analysis and gap findings
• Presenting options with pros, cons, and a clear rationale for one path forward for each recommendation
• Quantifying projected impact against established baselines: time saved, error reduction, cost avoidance, compliance risk addressed.
• Delivering a sequenced implementation plan tied to the firm’s strategic investment milestones

Own the thread from discovery through delivery by:

• Following the initial engagement, working with the UAT lead to create standard operating procedures after the technology team implements your recommendations, built from your own process maps and requirements
• Producing SOPs clear enough that a new hire can follow them without tribal knowledge and specific enough that compliance can audit against them
• Routing completed SOPs through the firm’s approval process; you are the producer, and final sign-off lives with the COO, CCO, and Director of Operations
• Flagging opportunities where AI tools could reduce manual effort or improve consistency in the workflows you document, so the technology team can evaluate and prioritize those opportunities in future phases

Advance the engagement efficiently by:

• Building working relationships with department leads across Advisory, Client Service, Operations, Compliance, Portfolio Management, Financial Planning, and Information Technology without wasting their time; if you need 90 minutes, coming prepared so you only need 60
• Presenting findings to the CTO and Director of Operations in formats that support decision-making within 48 hours of delivery
• Maintaining a detailed work plan with intermediate milestones, with weekly check-ins to align priorities and course-correct
• Managing your own interview schedules, coordination, and day-to-day priorities between check-ins

Engagement Details

Engagement type: Independent contractor (1099) or corp-to-corp

Compensation: The firm is accepting proposals with hourly rates between $75 and $125, commensurate with the scope of experience you bring to both workstreams.

Duration: 3-month initial engagement with defined milestones. Extension based on delivery.

Hours: Approximately 28 hours per week

Location: Primarily remote with periodic on-site in Boston for stakeholder interviews and workshops (estimate 1 to 2 days per week)

Start date: Q2 2026

Environment: RIA. Compliance is a design constraint that shapes every workflow and system decision. Everything you document must account for regulatory implications.

This role may be the one for you if:

• You document the truth clearly; if a workflow is inefficient, your deliverable says so with evidence and a recommendation, and you do not wait for permission to have an opinion
• You challenge how things are done, but you bring people along, because the staff you work with will live with whatever gets built from your recommendations
• You prioritize speed over polish; a half-page memo that lets the team ship this week is more valuable than a 40-page assessment that sits in a folder
• You default to a direct conversation over a formal alignment session, and when you’re on-site, your instinct is to walk over and ask your question rather than send a meeting invite
• You treat compliance as a design constraint, not a blocker, and your instinct when you hear "SEC regulation" is to build it into the workflow from the start
• You are results oriented, resourceful, and manage your own time effectively between check-ins
• You take ownership of your deliverables and continuously refine until the downstream consumer can act on them
• You are comfortable using AI tools in your own work and can recognize where they might improve the workflows you document, even if building those solutions is someone else’s job

Qualifications

• 3 to 5+ years in business analysis or operations roles, with experience embedded inside a company (not only external advisory)
• Demonstrated experience producing process maps, requirements documents, gap analyses, and standard operating procedures; bring samples
• Experience conducting stakeholder interviews and translating business language into technical requirements
• Strong written communication. Your primary output is documents, not code. If writing is not one of your top three professional skills, this is not the right engagement.
• Experience maintaining requirements traceability from elicitation through testing
• Familiarity with root cause analysis methods (fishbone, 5 Whys, or equivalent) and ability to apply structured analysis to business process problems
• Professional services or consulting orientation: you understand scoped engagements, milestones, and deliverable-based accountability
• Proficiency with Microsoft 365 (Word, Excel, PowerPoint, Visio or equivalent diagramming tool)

Bonus Points for:

• Active user of AI tools (ChatGPT, Claude, Copilot, or similar) in your professional work to accelerate analysis, draft documents, or identify patterns
• Experience working inside a regulated financial services firm: RIA, wealth management, broker-dealer, banking, insurance, or healthcare
• Familiarity with Salesforce (Sales Cloud, Financial Services Cloud) from an analysis and requirements perspective
• Experience with Salesforce Flow Builder, Microsoft Power Automate, or similar tools for workflow orchestration
• Experience with Jira, Azure DevOps, or similar tools for managing user stories and sprint handoffs
• Understanding of SEC, Reg S-P, or similar financial regulatory compliance frameworks
• Experience with service delivery model design or operations optimization in professional services firms

How to Apply: Business Process Analyst (Contract)

To be considered for this engagement, please submit the following:

Resume: Your current resume, with an emphasis on business analysis, process documentation, and stakeholder-facing work.

Work Samples (2 to 3): Please include at least:

• One process map or workflow diagram you produced
• One requirements document, user story set, or gap analysis
• Samples may be redacted or anonymized for confidentiality. We are evaluating structure, clarity, and usability, not the content of your former client's processes.

Proposed Hourly Rate: Please include your proposed hourly rate with your submission.

What to Expect

In our initial conversations, we will walk through the engagement in detail and ask you to share how you would approach the first two weeks of the Client Review workstream. Come prepared to discuss your thinking, not to present a deck. We are looking for evidence that you understand the cross-departmental synthesis challenge described in the job description and have a structured point of view on how to approach it.

What We Are Not Asking For

• No cover letter.
• No written proposal. We would rather hear how you think in a conversation.
• No references at this stage. That conversation happens after we have reviewed your materials and had an initial call.

Submission

Please send all materials to [email protected] with the subject line: Business Process Analyst, [Your Name]