For public-sector delivery teams and regulated operators
Ship one complete digital service.
A portal is only the surface. Prodmake helps public institutions, delivery partners, and regulated operators turn one important service journey into production software—from account access and application through review, decision, status, notification, administration, deployment, and operation.
From $35,000. Larger platforms scoped separately.
Best suited to programs with a responsible sponsor, known users and operators, a service that can be bounded, and a credible path to procurement or delivery authority.
Ad measurement: Checking… Privacy choices
We use Meta to measure visits and applications. When enabled, Meta receives browser identifiers and, for eligible applications, your IP address, hashed email and an application event. Your project answers are not sent. This is optional; the form works either way.
The problem
A portal can expose a form without delivering the service.
A complete digital service connects the public experience to the operating system behind it. Identity, rules, review, decisions, exceptions, status, notifications, administration, integrations, and production ownership must work as one accountable journey.
- 01
Applications enter through a portal, but processing continues through email and spreadsheets.
- 02
Identity, eligibility, and entitlement decisions are fragmented across systems.
- 03
Review and approval states are implicit, inconsistent, or difficult to audit.
Relevant production work
Experience inside systems where public trust and operational correctness matter.
Frontend foundations and reusable interface primitives for citizen accounts and national public services.
Kazakhstan e-government systems
View case studyNational-scale citizen-service experience coordinated with roughly 50 backend engineers and public-sector stakeholders.
The work established durable account and data-access behavior across long-lived public-service surfaces. It is relevant production experience, not a claim that Prodmake alone delivered the wider national platform.
AuditBoard
Production engineering under enterprise correctness and maintainability requirements.
Application, service, and infrastructure work inside an enterprise audit, compliance, and risk platform.
Scoutbase
4,000+ maritime workers supported through production workflows.
Safety and support workflows for maritime workers operating under unreliable connectivity.
The first engagement
Modernize one service far enough to operate.
The first stage defines one complete journey and implements the public, operator, product, integration, administration, and production obligations required to run it. It creates a credible foundation for expansion without pretending the wider platform is a fixed-price first step.
- 01
Written service model covering actors, rules, states, decisions, exceptions, and outcomes.
- 02
Citizen, customer, partner, or operator experience for the accepted journey.
- 03
Account, identity, eligibility, and entitlement boundaries required by scope.
- 04
Workflow logic for application, review, decision, status, and notification.
Starting investment
From $35,000
What the first-stage commitment means
The delivery plan is set only after the service boundary, authority, policy rules, security constraints, integrations, environments, acceptance criteria, and procurement path are understood. The clock begins when the accepted scope is funded and the required access, owners, and decisions are available.
- The first stage must end in a usable and operable service outcome, not only a strategy document or portal mockup.
- External approvals, procurement, unavailable environments, and third-party dependencies remain explicit schedule constraints.
- Larger platform obligations are sequenced as additional stages instead of being hidden inside the initial commitment.
What your organization needs to provide
Plan for 2–4 hours each week across one accountable sponsor, the workflow owner, and the responsible data, security, or system owners.
- Accelerated pace requires one-business-day blocking decisions and ready access to the named owners.
- Managed pace allows up to three business days for decisions and schedules delivery around procurement and review windows.
- External approvals and unavailable owners remain explicit dependencies; they do not become hidden implementation time.
What this stage does not include
- Modernizing every service or replacing the whole platform at once.
- Undecided policy, institutional ownership, or procurement work.
- Unlimited integrations, historical migration, or cross-agency reconciliation.
- National identity replacement or company-wide ERP replacement.
- Formal security, accessibility, regulatory, or procurement certification.
- Open-ended requirements after scope acceptance.
- Continued operation beyond the accepted stage unless separately scoped.
Start with the service that must work end to end.
Describe the users, application or request, review and decision path, current systems, recurring exceptions, responsible operators, and the production outcome the first stage must deliver.
Human review. If the fit is credible, expect a written reply with the appropriate next step, usually within two business days.