Software for your business.

Turn a manual workflow into working software, or get an unfinished product into production. Prodmake connects product decisions, design, engineering, and release under one agreed scope.

Engagements start from $12k

Proof before promises.

Kuan’s client and employment experience spans offline work, mobile releases, enterprise risk, and national public services. Each case explains the work and its context.

Scoutbase / Workerline.ai

Scoutbase logo Scoutbase

“Kuan was absolutely pivotal for our success. His expertise paved the way for our growth and enabled us to acquire the trust of investors and additional funding.”

Yassin Askar
Co-Founder, Scoutbase

Operating result

4,000+ workers supported in production

Offline work and intermittent connectivity made synchronization and trust non-negotiable.

Kuan’s client / fractional CTO work · 2018–2025

View Scoutbase case study

Lane Technologies

Lane Technologies mark TECH

“The infrastructure Kuan built became a key asset during our acquisition due diligence.”

Andy MacDonald
Engineering Director, Lane Technologies

Due-diligence evidence

Release infrastructure used in acquisition due diligence

Release reliability became commercially important as the product scaled.

Kuan’s employment · 2019–2020

View Lane case study

AuditBoard

AuditBoard logo

Production engineering inside an enterprise platform for audit, compliance, and risk.

Production scope

Production changes across application, services, and infrastructure

Enterprise risk workflows demanded correctness and maintainability.

Kuan’s employment / contract work · 2022–2023

View AuditBoard case study

my.egov.kz / eGov.kz

Kazakhstan national emblem my.egov.kz PUBLIC SERVICES

The personal account layer behind citizen access to Kazakhstan's digital public services.

Interface foundation

Reusable interface foundations for national citizen services

Citizen-facing services needed durable foundations at national scale.

Kuan’s lead frontend contribution · 2013–2015

View Kazakhstan eGov case study

What needs to work next?

A business workflow that needs software. A product that needs to reach production. Start with the work you need taken off your hands, then agree the smallest useful outcome.

Your team is keeping the workflow together by hand.

Requests arrive in one place, approvals happen in another, and someone keeps a spreadsheet up to date. You know the process. You need it to work without that chain of manual handoffs.

What you can commission

A working system for one agreed process, including the user experience, permissions, records, integrations, and an operator’s way to handle exceptions.

Relevant experience

Scoutbase: Kuan’s client / fractional CTO work connected worker-facing software, offline synchronization, backend systems, and ongoing operation.

See the Scoutbase work

The product works. Getting it released doesn’t.

You have a prototype or an existing codebase, but the release depends on unfinished integrations, manual steps, or knowledge held by one person. Adding features won’t resolve that.

What you can commission

A bounded build or completion scope carried through testing, deployment, and handover, with the release responsibilities written down.

Relevant experience

Lane Technologies: in an employed engineering role, Kuan built mobile release and delivery infrastructure later cited in acquisition due diligence.

See the Lane work

A working demo is not an operating product.

The prototype proves an idea can be shown. Production proves customers and the business can depend on it.

What the prototype proves

The happy path can work.

  • A user can see and try the main interaction.
  • The concept is concrete enough to discuss.
  • The fastest implementation choices got it moving.

What production must prove

The business can rely on it.

  • Users, permissions, data, and edge cases behave deliberately.
  • Payments, integrations, administration, and recovery are operable.
  • Releases are tested, observed, and owned after launch.

Prodmake closes that gap. The deliverable is not more code; it is a product that can carry real responsibility.

One product. One accountable production loop.

Prodmake owns the connected work from product definition through the systems that keep it running.

Customer experience

Where customers and operators use the product

Product decisions become one coherent experience across every customer surface.

Product core

What makes every interaction work

Each action passes through shared rules, data, and integrations instead of isolated features.

Operating layer

What keeps the product reliable after launch

Every release is deployed, observed, administered, and fed into the next product decision.

Define. Build or rescue. Operate.

A clear scope can go straight to Build or Rescue. Use paid Definition only when important unknowns prevent responsible scoping. Add ongoing operation when a live product needs it.

  1. Define

    Starts with: Market knowledge, evidence, and constraints

    Turn what you know into explicit users, workflows, UX, data, architecture, acceptance evidence, and the first production scope.

    Outcome A written production plan

    This is not generic discovery or a paid estimate. The plan must be useful and inspectable on its own.

  2. Build or rescue

    Starts with: Agreed decisions or a product that has stalled

    Implement or repair the interfaces, backend, integrations, administration, deployment, and launch path.

    Outcome Software running reliably in production

  3. Operate

    Starts with: A live product and real usage signals

    Observe, administer, repair, and improve the system as customers and operations reveal what matters next.

    Outcome A product that keeps improving

Each commitment stands on its own. A useful plan, an accepted production outcome, or bounded ownership of a live product—not a mandatory three-stage package.

Choose the first commitment

Production Build or Rescue

From $12,000

Most complete scopes: $35,000–$75,000

The outcome is clear enough to scope. Commission the build, completion, or repair through deployment. The minimum covers one tightly bounded outcome.

Production Definition

$12,000–$15,000

Only when material decisions remain unresolved

Buy a written production plan when workflow, scope, or technical unknowns prevent a responsible build proposal. It is useful whether or not Prodmake builds it.

Product Operations Partner

$15,000–$25,000 / month

For a live product that needs ongoing ownership

Agree monthly priorities, capacity, response expectations, and operating outcomes. This is not unlimited development or 24/7 incident response.

Planning ranges in USD, not fixed quotes for an entire product. The proposal sets the scope, staffing, start conditions, payment milestones, and acceptance criteria. Larger work is staged.

Decide

Scope and tradeoffs

Review

Human checkpoint

Operate

Launch and observe

Clear leadership. Delivery shaped around the work.

Kuan leads each engagement across product, design, and engineering. The proposal sets out his direct work, any additional specialists required, and responsibility for review, launch, and agreed support. Prodmake remains your delivery partner.

Kuan, founder of Prodmake

Founder-led delivery

Kuan

Founder and technical lead

13+ years in production systems

Decisions stay connected to implementation.

Scope, tradeoffs, and technical decisions stay written and visible. Roles, specialist involvement, and acceptance are agreed before delivery begins.

Know what you’re accepting before work begins.

You should not have to infer progress from hours logged or screenshots. Agree the evidence, decisions, and handover that will let you judge the work.

Before you commit
A written scope names the production outcome, exclusions, delivery roles, client dependencies, price, and acceptance checks. Unconfirmed specialist capacity is identified before a start date is agreed.
At delivery reviews
Inspect working behavior against the agreed checks. Written updates separate completed work, open risks, and decisions needed from you. Scope changes require a tradeoff or change order.
At acceptance
Review the agreed workflows and failure cases, with test or demonstration evidence. Record unresolved items and who owns them rather than treating deployment alone as acceptance.
At handover
Receive the agreed documentation, repository and environment access, release and recovery instructions, and support boundaries. Continuing operation is a separate commitment when it is needed.

Useful tools. Human responsibility.

AI-assisted research, implementation, and checks support delivery where appropriate for the project’s data and security requirements. They do not replace specialist expertise, human review, or agreed support arrangements.

Parallel execution. One line of responsibility.

Research, implementation, verification, and operating checks can run at once. Tradeoffs, acceptance, and release remain human decisions.

Why this model works.

You bring market truth. Prodmake turns it into connected product decisions, production software, and operating evidence.

You bring the market
Firsthand knowledge, customer access, commercial judgment, and decision authority.
Prodmake carries the product
Agreed responsibility across scope, UX, engineering, integrations, launch, and support.
Evidence drives the next move
Written decisions and operating signals replace guesswork, handoff loss, and roadmap theater.

Before you commit.

Do we have to buy a discovery phase first?

No. If the outcome and implementation constraints are clear enough, start with Production Build or Rescue. Production Definition is paid work only when material unknowns need resolving. It produces a usable plan, not a paid estimate or a cheaper substitute for a build.

Can you work with our existing team or codebase?

Yes, where the responsibilities and access can be agreed. The scope can cover a module, integration, release path, or bounded repair rather than a full rebuild. The proposal separates Prodmake’s work from your team’s work and names who reviews and accepts it.

How much time will you need from us?

You provide someone who can make decisions, explain the real workflow, arrange access, and accept the result. We agree review points and availability before starting. Prodmake owns the contracted product and engineering work; your business, compliance decisions, and third-party dependencies remain yours.

How soon can we start, and how long will it take?

After scope, capacity, payment, access, and required inputs are confirmed. The proposal sets a delivery window around those dependencies. A deadline alone is not enough to promise a date; larger products need staged commitments.

What happens after handover?

The proposal sets documentation, code and IP terms, third-party licenses, access, and any included support period. Your team can take over the agreed operating responsibilities. Where continuing ownership is useful, Product Operations Partner is scoped separately; it is not a required subscription.

Can you meet our security or procurement requirements?

Share them before scoping. We need to check data handling, access, vendor eligibility, staffing, and support requirements against the actual engagement. Prior enterprise experience is not a security certification or a promise that every procurement condition can be met.

Tell us what needs to work.

Start with your current workflow or product, what is getting in the way, and the result you need. Then choose a fit call or continue in writing.