Service Product Manager

Appunite is turning its AI Transformation work - proofs of concept and lessons from real client projects - into a repeatable service product. One validated by the market, not by internal slide decks, and meant to become a core part of what we offer. We need someone to own it.

This is a product role, not a coordination role. You'll define what success looks like for the service, run discovery with client sponsors, domain experts and end users, turn what you learn into hypotheses and experiments, and shape every next version. You'll also own the less glamorous part: a backlog of dozens of interlinked items - documentation, tools, processes, reviews - that need to click into place before v1 is real.

You'll make sure what Sales promises is what Delivery actually delivers. That means working closely with GTM, Client Success and Service Delivery leads, plus designers, engineers and outside consultants - none of whom report to you. In your first months you'll work side by side with the initiative's lead, then gradually take over full ownership of the product.

Fair warning: some of our key hypotheses will take time to validate. If you keep momentum and sharp thinking when data is slow to come in - and you'd rather build a strategic product than manage a team - this is built for you.

What we offer

• Salary: 16 000 - 22 000 PLN net/month B2B - depending on your experience

• Remote first approach

• Real product ownership of a service meant to become core to Appunite's offer

• A ~1.5-2 year path to a full v1, with room to take the service beyond its initial vision in v2 and v3

• Fast onboarding - about 4 pages of project docs, a few conversations, and you're working on real topics within a week

• Dedicated focus on one initiative, not split across unrelated projects

• Design support from a dedicated consultant, so you can focus on the product

• You've owned a product or service from an early stage - defining success, setting metrics and deciding what goes into the next version, not just executing someone else's backlog.

• You've run discovery yourself: interviewed sponsors, domain experts and users, synthesized repeating and conflicting signals, and separated the real problem from a premature solution.

• You've been the glue across multiple departments without a dedicated team - aligning people through influence, not hierarchy.

• A hands-on mindset - you start by checking actual state against the plan, then move into decisions and execution. You challenge assumptions constructively and don't default to the loudest opinion in the room.

• Strong delivery and project management skills: backlog management, prioritization, keeping people and deadlines in sync, and reliably getting things over the line.

• You keep your pace when hypotheses take longer to validate, and you change course when new data says so instead of defending the original plan.

• You factor client and user experience into every decision about the service, even though you're not the designer.

• Fluent Polish and English.

Nice to have

• Experience in service design, especially working with service blueprints - not required, but it sharpens how you close the gap between current and target state.

• Curiosity about AI Transformation, UX and critical business workflows, and appetite to grow your skills in these areas.

Responsibilities

• Define the service's North Star, implementation success metrics, key attributes and the moments of truth in the client and user experience.

• Run discovery: interviews with sponsors, domain experts and users, research into critical workflows, and synthesis of what you hear.

• Turn signals from clients and internal teams into hypotheses, experiments, priorities and next versions of the service.

• Protect continuity between the sales promise and delivery - agreed outcomes and experience have to survive the hand-off to the delivery team.

• Design the service end to end on a blueprint - from pre-sales, through sales and hand-offs, to delivery - then build the missing tools from the backlog.

• Own and prioritize the initiative's backlog (kanban) - track dependencies, what's shipped, what needs review and what's blocking progress.

• Coordinate GTM, Client Success, Service Delivery, designers, engineers, integration/automation specialists and external consultants.

• Drive the creation of documentation, processes and reports that stand on their own - not dependent on one person's memory.

• Keep a weekly rhythm - make sure the initiative visibly moves forward every week, even when things are ambiguous.

• After launch, keep iterating: observe, validate hypotheses, and shape v2 and v3 of the service.