Business Analyst | Requirements Documentation, Process Mapping, & UAT | Turning vague ideas into developer-ready specs

I'm a Business Analyst who started in QA, and that origin shapes how I work. Testing gave me an eye for what breaks and why. Business analysis taught me to understand the systems, the processes, and the people using them. Add design thinking and project delivery experience, and you get a BA who can carry an idea from discovery interview to wireframe to spec to validated build.

What I do for clients:
→ Requirements documentation — user stories, acceptance criteria, and BRDs in language both stakeholders and developers understand
→ Process mapping & SOPs — documenting how your business actually works, so your team can run it without you
→ Wireframing & prototypes — turning requirements into visual mockups in Figma, so your developers build from a picture, not a guess
→ UAT — and here my QA roots become your advantage: I test the finished build against the very requirements I wrote. One person accountable for "what we agreed" matching "what was delivered."

What sets me apart: I don't just document requirements, I challenge them. I don't just test features, I ask why they were built. I don't just manage timelines, I protect them.

Currently available for freelance engagements and open to long-term contracts. If your project needs someone who asks the right questions before a single line of code is written, let's talk.

Work Terms

Every project starts with a scoping call. I write a one-page scope with deliverables, timeline, and price. No work starts until we both sign off.

For process work, I map the current process and flag gaps first. Improvements come after, as a separate phase.

Payment
Fixed price for scoped projects, hourly for advisory work at [$X/hour].
Fixed price: 50% upfront, 50% on delivery. Projects over four weeks split into milestones. All payments through Guru.

Turnaround
- Single process map or user story set: 3 to 5 business days
- Full requirements package: 2 to 3 weeks
- UAT plan and test cases: 1 to 2 weeks

Timelines start once I can reach the systems and people I need. Delays shift the timeline by the same amount, and I flag it immediately. Rush work: 25% premium, subject to my load.

Availability
Monday to Friday, 9am to 6pm Philippine time (UTC+8). Morning overlap with Australia and Asia. Evening overlap with US Eastern. Calls outside these hours with notice.

Communication
I reply within one business day. Guru messaging works, or I can join whatever channel your team already uses. Weekly check-in on longer projects. If something is off track, you hear it from me first.

Revisions
Two rounds included on every deliverable. New requirements are new work, quoted before I start.