Company Description FlatOut Solutions helps organizations enhance sales processes, improve customer support, streamline marketing, and automate operations to boost efficiency and productivity. By integrating tailored services and technology, the company focuses on reducing operational costs while strengthening business performance. FlatOut Solutions works closely with clients to understand their goals and deliver practical, results-driven solutions. Team members have the opportunity to contribute to impactful projects that directly influence customer success and business growth.
Role Overview
As a Product Owner, you own what gets built and why. You work directly with clients to understand their business, translate what you learn into a clear backlog, and design the flows behind it.
Your most important contribution is perspective. Engineers verify that features work as written. You verify that what was built actually makes sense for the client's business, and you catch the gaps between the two before the client ever sees them.
We run several engagement models: monthly retainer, time and materials, fixed price with capped hours, and fixed price. What holds across all of them is that the client directs prioritization on an ongoing basis, and requirements get worked out through iteration rather than settled in a specification up front. Some engagements carry an hour cap and an explicit out-of-scope list; others deliberately carry neither. Getting agreement on what a piece of work actually means, before the team builds it, is the heart of this role.
What You'll Own
Discovery and product definition
- Work with clients to understand their business, their workflows, and what they actually need, not just what they asked for
- Translate that into epics, stories, and acceptance criteria in Jira that engineers can build against
- Own scope definition: recommend and define requirements for client approval, and guide the client on scope and trade-offs so the work adds up to something complete rather than half-finished
- Agree scope interpretation with the client at the epic level, in writing, before the team builds against it
- Keep the backlog sequenced and current as the product evolves. The client sets priority order; you make sure what sits behind each priority is unambiguous before it reaches the team
- Reduce the load on stakeholders by doing the thinking upfront and bringing them decisions rather than open questions
UX design
- Design the user journey end to end: flows, information architecture, and wireframes
- Keep complex operational workflows simple to navigate for the people who use them every day
- Validate the flows with the client before engineering starts
- Hand off clear UX foundations to the Product Engineers and review the built UI against them
Acceptance
- Run acceptance on complete end-to-end workflows, before anything reaches the client. On ongoing engagements there is no milestone gate behind you, so this is the last structured review before production
- Evaluate what was built from the client's perspective and flag anything that is technically correct but wrong in practice
- Feed those findings back into the backlog as refinements, and close the loop with the team
Client partnership
- Act as the primary product point of contact, leading requirements and feedback conversations
- Manage expectations honestly and explain product trade-offs in plain language
- Turn client feedback into concrete product decisions
What This Role Does Not Own
- System architecture and technical design decisions, which sit with the Product Engineering Team Lead
- Code review and test strategy
- Visual and UI design. You define the flows and the structure; the Product Engineers design and build the interface against an established design system
Requirements
- Proven experience as a product owner or product manager, owning a product from discovery through acceptance
- Strong UX capability: user flows, wireframes, and information architecture that make complex workflows easy to navigate
- Create epics, stories, and acceptance criteria in Jira detailed enough to build against
- Ability to learn a client's business domain quickly, hold their perspective while reviewing what was built, and stay technically fluent enough to work closely with engineers
- Experience running acceptance across full workflows, with an eye for gaps
- Proficient with an AI-accelerated design and prototyping tool such as Claude Design
- Comfortable working where priorities shift week to week and clarity is something you create rather than receive
- High discipline and proactive communication in a distributed team
- Available during core collaboration hours, 6:00 AM to 10:00 AM Pacific Time, Monday to Friday
Nice to Have
- Familiarity with established design systems and their conventions, for example ShadCN UI
- Experience in an agency or consultancy, working across several clients and stakeholder sets