Business Analyst / Product and QA Lead for Water Subscription Platform
About the project
We are building a new website and platform for a premium water delivery company. Customers subscribe to regular water deliveries. They pay a deposit for reusable water containers and return them later.
The platform will include:
- A public website and product catalog
- A tool to check if delivery is available in a ZIP code
- A subscription builder (products, sizes, quantities, frequency, discounts, deposits)
- Online payments and a customer account area
- Delivery tools: delivery lists for drivers, a mobile-friendly driver app, and delivery photos
- Inventory tracking and demand planning - to track containers and deposits etc. (given, returned, damaged, lost, refunded)
- Automatic customer messages (reminders, delivery confirmations)
- Connections to a payment provider, GoHighLevel (CRM), and QuickBooks
Tech stack: Next.js, TypeScript, Tailwind, Supabase (database, login, file storage), Vercel, GoHighLevel, QuickBooks, Payments - Card Connect with Recurring billing.
We already have a prototype and a first draft scope document. These are a starting point. Your job is to turn them into a clear, complete plan.
You will be the main link between the client, and the team - the designer, the developer.
What you will do
This role combines 2-3 roles in one: Product/Business Analyst, QA and potentially , Project Manager. We want one person who owns the requirements, the plan, and the quality.
1. Lead the Discovery phase (first 1-2 weeks)
- Run meetings with the client to turn ideas and notes into clear, written requirements
- Get clear answers on the tricky business questions
- Map out how each integration (payments, GHL, QuickBooks) should work, step by step
- Deliver: a product backlog, a data model (with Alex), a list of risks, and a clear MVP scope (what is included and what is not) and estimates
2. Define and prioritize the product
- Help decide what belongs in the MVP and what can wait.
- Write user stories that are clear enough for the developer to build without extra meetings
- Keep the backlog organized and up to date; run planning meetings and demos
- If something doesn't fit the plan, say so early, explain why, and suggest an alternative
3. Manage the project
- Keep track of the plan, deadlines, and what depends on what
- Report progress weekly to us and the client
- Help the developer get what they need: decisions, content, images, account access
- Be honest with the client if a deadline is at risk
4. Own quality (QA)
- Write test cases based on the requirements
- Test the website and app
- Focus on the tricky cases, not just the easy ones: payment errors, duplicate charges, subscription changes, deposit calculations, and permissions
- Keep track of bugs with clear steps to reproduce them
- Plan and run testing with the client before launch
- Check basic accessibility on customer-facing pages
What we're looking for
Must have
- 4+ years of experience as a Business Analyst or Product Owner on custom web projects, including some QA or delivery management
- Experience writing requirements, product backlog, etc.
- Strong written English (you'll write most requirements and talk directly with a US client)
- Comfortable with technical ideas: databases, APIs, webhooks, and user permissions. You don't need to code, but you should be able to question a technical design
- Hands-on experience with manual QA, including testing APIs (e.g. with Postman)
- Able to work independently in a small team
- Use AI consciously to improve BA and QA efficiency
Nice to have
- Experience with e-commerce, delivery, or logistics platforms
- Experience running Agile projects (Scrum or Kanban) as the person responsible for the plan
- Experience integrating a US payment provider with recurring billing (CardConnect, Stripe, or similar)
- Experience with GoHighLevel (or other CRM) or QuickBooks
- Familiarity with Next.js and Supabase
- Experience with automated testing (Playwright or other) even with AI
- Comfortable reviewing designs in Figma
You are a good fit if you:
- Write things down. If a decision isn't written down, it doesn't count
- Are comfortable telling a client that something won't fit in the MVP
- Ask questions instead of guessing
- Care that the product works well in real use, not just that a task is marked "done"