Engagement options
Each engagement has a defined purpose, clear ownership, and a path to handover. Work starts at 10,000 PLN or €2,500, quoted in the contract currency.
01 · First engagement
For teams facing an expensive AI, architecture, or delivery decision before build begins.
See DiscoveryFor one bounded agentic, retrieval, or workflow capability with an owner, available context, and an agreed delivery team.
Architecture and delivery leadership, evaluation and exception paths, human-review controls where needed, deployment, documentation, and handover.
Discuss a Production SprintFor product teams with delivery risk, an architecture gap, or a need for senior technical direction and accountable delivery leadership.
Technical roadmap and architecture, quality bar, AI-system evaluation and governance, scope, access model, and handover.
Discuss technical directionHow I work
I work as the accountable principal with your product and engineering team, or lead an agreed delivery team: in agreed repositories, delivery rituals, and communication channels. Implementation needs confirmed development capacity before it is committed. You retain product decisions, code, infrastructure, and documentation. Scope, access, decision rights, and handover are agreed before work begins.
Discovery, technical direction, architecture, quality, and delivery leadership.
Confirmed development capacity, product ownership, relevant access, and domain context.
Acceptance criteria, key decisions, working handover, and client ownership.
Secondary path
For a costly operations or knowledge-work process, Discovery establishes whether automation creates enough value to justify a build. The result can be a recommendation not to automate.
Bring a workflow problemStart cleanly