Structured Engagements.
Working Software Delivered.

Every ADM package delivers production-ready software — not planning documents, not prototypes. Powered by nine intelligent agents and frontier AI coding models, with Predikly absorbing all delivery risk.

✓ Scoped to your challenge — no hourly billing
✓ Working software in every package
✓ We absorb the delivery risk
ADM Packages

Four Packages.
Every One Delivers Working Software.

New product or existing codebase — each ADM package is scoped by complexity, not by hours. Contact us for a proposal tailored to your engagement.

Spark
A complete functional product or meaningful enhancements — fast.
Contact Us for Competitive Pricing
3–4 weeks
What you get
3–5 features (new product) or 2–3 enhancements (existing)
Working frontend + backend + database
Tested and deployment-ready
AI-powered codebase analysis (existing systems)
Regression coverage included
Scope boundaries
Integrations: 1–2
Existing codebase: Under 80K lines
User roles: 1–2
Get Started →
Most Popular
Launch
A full MVP or significant system evolution — ready for real users.
Contact Us for Competitive Pricing
5–6 weeks
What you get
5–8 features (new) or 4–5 enhancements (existing)
Multiple user roles with RBAC
CI/CD pipeline configured
Security review embedded throughout
Schema migrations + regression suites
Handoff documentation package
Scope boundaries
Integrations: 2–3
Existing codebase: 80K–200K lines
User roles: Up to 3
Get Started →
Scale
Complex products or large-scale legacy evolution with governance.
Contact Us for Competitive Pricing
8–10 weeks
What you get
8–12 features (new) or 6–7 enhancements (existing)
Complex RBAC with up to 5 user roles
Production deployment with monitoring
Cross-service changes + schema migrations
Knowledge transfer session included
Scope boundaries
Integrations: 4–5
Existing codebase: 200K–500K lines
User roles: Up to 5
Get Started →
Transform
Enterprise-grade, multi-system delivery with full governance.
Contact Us for Competitive Pricing
11–13 weeks
What you get
12–16 features (new) or 7–8 enhancements (existing)
Up to 8 user roles with complex permissions
Full governance documentation + audit trails
Predictive monitoring + alerting
Two knowledge transfer sessions
Dedicated Predikly technical lead
Scope boundaries
Integrations: 6–8
Existing codebase: 500K–800K lines
User roles: Up to 8
Get Started →
Enterprise & Custom Engagements
Need Something Larger?
Let's Design It Together.
Multi-product portfolios, organisation-wide automation programmes, regulated industry deployments with formal certification, or ongoing delivery partnerships that don't fit a single package — we build custom engagements for enterprise scale.
Contact Us → sales@predikly.com
Scope Clarity

What Counts as a Feature?

A feature is a self-contained unit of functionality a user can interact with to accomplish a specific goal. Here's how we count — so there's no ambiguity when scoping your project.

Each of these is ONE feature
User authentication — signup, login, password reset, session management. One functional unit, one feature.
Dashboard with filters — key metrics, date ranges, export capability. One screen, one purpose, one feature.
Notification system — in-app alerts + email notifications. One communication layer, one feature.
File upload module — upload, preview, manage, delete. One capability, one feature.
Invoice generator — create, preview, download as PDF. One workflow, one feature.
Search with filters — query input, filter panel, results display. One interaction pattern, one feature.
Third-party integration — connecting to Stripe, a payer API, or a CRM. One integration, one feature.
Role-based permissions — admin, editor, viewer with access controls. One permission model, one feature.
These are NOT a single feature
"An e-commerce platform" — that's an entire product containing 15–25 features. It needs to be decomposed.
"Reporting and analytics" — too vague. A single report with filters = 1 feature. A full analytics suite with multiple report types, scheduling, and export = 3–4 features.
"User management" — if it means basic CRUD for users, that's 1 feature. If it means users + roles + permissions + audit logging + SSO integration, that's 3 features.
"Complete backend" — not a feature. The backend is the technical layer that supports multiple features.
The Decomposition Test
If you can remove a feature and the rest of the application still works and makes sense, it's correctly scoped as a single feature. If removing it breaks three other things, it might be too tightly coupled and needs to be counted as part of a larger feature — or the dependencies need to be counted separately.
Real Examples

What Each Package
Looks Like in Practice.

Greenfield builds and existing codebase enhancements — here's how real projects map to each package tier.

Greenfield
Spark
Internal Expense Reporting Tool
Employee expense submission, manager approval workflow, finance processing view, email notifications, and basic spend reporting. A complete, usable internal tool in 3–4 weeks.
Submission formApproval workflowFinance viewNotificationsReporting
Enhancement
Spark
Retail Order System — 3 Enhancements
New returns workflow with automated status tracking, improved product search with filters, and an updated operations dashboard. Full codebase analysis included.
Returns workflowSearch upgradeDashboard refresh
Greenfield
Launch
B2B SaaS Product — Full MVP
Authentication with SSO, guided onboarding flow, core workflow engine, admin console, reporting dashboard, notification system, Stripe billing integration, and transactional email. Launchable in 5–6 weeks.
Auth + SSOOnboardingCore workflowAdmin panelReportsNotificationsStripeEmail
Enhancement
Launch
Healthcare Patient Management — 5 Enhancements
Add telehealth scheduling module, redesign patient intake form flow, build new provider dashboard, integrate with a payer authorization API, and add audit logging across all modules.
TelehealthIntake redesignProvider dashboardPayer APIAudit logging
Greenfield
Scale
Fintech Lending Platform
Borrower application flow, credit scoring integration, automated underwriting workflow, lender dashboard, document management system, notification engine, admin console with RBAC, partner API, and full audit trail.
Application flowCredit scoringUnderwritingLender dashboardDoc managementPartner APIAudit trail
Enhancement
Scale
Manufacturing ERP — 7 Enhancements
Modernise 3 legacy reporting modules, add real-time quality monitoring dashboard, integrate 2 new IoT sensor platforms, and migrate critical database schemas for performance. Knowledge transfer included.
3× module modernisationQuality monitoring2× sensor integrationSchema migration
Greenfield
Transform
Enterprise Process Automation Platform
Visual process designer, agent configuration engine, business rule engine, multi-system connectors (ERP, CRM, HRIS), audit trail, admin console with multi-tenant RBAC, monitoring and alerting, API gateway, and reporting suite.
Process designerAgent configRule engineMulti-system connectorsAudit trailMulti-tenant RBACMonitoringAPI gateway
Enhancement
Transform
Financial Services Trading Platform — Major Overhaul
Modernise order management module, add real-time risk monitoring, integrate 3 new market data providers, build regulatory reporting, migrate 4 critical domains from monolith to microservices, and implement full audit trail.
Order managementRisk monitoring3× data providersRegulatory reporting4× microservices migrationAudit trail
How We Decide

Your Project's Complexity
Determines the Package.

We score every project across these dimensions before committing to an ADM package. If your project scores higher on two or more dimensions, it moves to the next tier.

Spark
Contact Us
Timeline
3–4 weeks
Features
3–5 new / 2–3 enhancements
Existing codebase
None or under 80K lines
Integrations
1–2 external systems
User roles
1–2 simple roles
Launch
Contact Us
Timeline
5–6 weeks
Features
5–8 new / 4–5 enhancements
Existing codebase
80K–200K lines
Integrations
2–3 external systems
User roles
Up to 3 with RBAC
Scale
Contact Us
Timeline
8–10 weeks
Features
8–12 new / 6–7 enhancements
Existing codebase
200K–500K lines
Integrations
4–5 external systems
User roles
Up to 5 complex roles
Transform
Contact Us
Timeline
11–13 weeks
Features
12–16 new / 7–8 enhancements
Existing codebase
500K–800K lines
Integrations
6–8 external systems
User roles
Up to 8 roles
Common Questions

Engagement FAQ

What if my project doesn't fit neatly into one package?+
We score your project across six complexity dimensions. If it scores higher on two or more dimensions than the package you'd expect, it moves to the next tier. This protects both sides — you get a realistic timeline, and we can deliver without cutting corners. We'll walk you through the scoring in the initial conversation.
What happens if requirements change after we start?+
Fixed price doesn't mean unlimited scope. We sign a clear scope agreement before kickoff with explicit boundaries. If requirements change materially during the engagement, we'll assess the impact together and re-evaluate the package tier if needed. Minor refinements within the agreed scope are expected and handled naturally.
How is this different from hourly billing?+
With hourly billing, you pay for time spent — and you never know the final cost until the project ends. With our packages, you know the price and timeline before we start. We absorb the delivery risk. If our agents complete the work faster, that's our efficiency — your price doesn't change. If complexity surfaces, we handle it — your price still doesn't change.
Can I start with Spark and upgrade later?+
Absolutely — that's the most common path. Many clients start with Spark to experience the agentic delivery model on a bounded scope, then expand to Launch or Scale for the next phase. Each engagement is independently scoped and priced. There's no lock-in and no minimum commitment beyond the current package.
What do I need to provide before kickoff?+
For new products: stakeholder availability for the first week, and clarity on the core user problem you're solving. For existing codebases: codebase access, environment access, and any available documentation within the first week. The faster we get context, the faster we deliver. Delayed access extends timelines proportionally.
Do you work with existing codebases or only greenfield?+
Both. Every package supports either a new product build or enhancements on an existing codebase. For existing systems, we use Claude Code, OpenAI Codex, and Gemini Code Assist to deeply understand your code before any enhancement work begins — architecture mapping, dependency documentation, and technical debt assessment are included in every package.
Do you handle compliance requirements (SOC2, HIPAA, etc.)?+
Security best practices and compliance awareness are built into every package — from code-level security scanning to audit trail generation. For projects requiring formal compliance validation (SOC2 certification, HIPAA compliance documentation, PCI-DSS, GDPR), we scope that during the intake conversation based on your specific requirements. Formal compliance work may adjust the package tier depending on the depth of validation needed.
What's included in the "knowledge transfer" sessions?+
A structured handoff session with your engineering team covering architecture decisions, code organisation, deployment procedures, and ongoing maintenance guidance. Scale includes one session; Transform includes two (one for engineering, one for leadership). The goal is that your team can confidently own and extend the system after the engagement.
What if we need ongoing support after delivery?+
Post-delivery support can be arranged as a separate engagement — typically scoped as a Spark-level package for ongoing enhancement work, or a custom support agreement for production monitoring and maintenance. We'll discuss options during the knowledge transfer.
Ready to Start?

Let's Scope Your Project
in a 30-Minute Conversation.

Tell us what you're building or what needs to change. We'll identify the right package, walk you through the scope, and give you a clear timeline — no obligation.

Book a CXO Briefing Download Platform Overview

Direct conversation with senior technical leadership. No intermediaries. No pitch decks.