Core Plans are built for routine maintenance, urgent technical needs, fresh starts and step by step product work. You choose the operating capacity. Orzed keeps the work visible, reviewable and ready to grow without resetting the system each time the scope changes.
WHAT CORE PLANS ARE FOR
Core Plans are designed for lighter systems, fresh builds, urgent needs and gradual execution inside the Orzed Console. Use them for routine maintenance, startup work, AI-assisted tasks, integrations and technical guidance without forcing the project into a larger structure too early. The same plan carries build, maintenance, advisory and AI execution; capacity grows only when the work asks for it, and delivery memory stays alive across every cycle.
Routine fixes and first moves
For routine maintenance, urgent fixes, early product shaping and AI-heavy tasks with light expert contribution. Best when the work is real but still narrow.
Runs on 4,000 Operating Credits per month inside one active work lane, with standard agent access, shared delivery ownership and a monthly maintenance readout. A +10% burst window covers short pressure spikes without forcing a plan change.
Small but steady execution
For companies that need more than small fixes but still want a lean structure. Works well for recurring maintenance, small product improvements, integrations and AI-assisted execution with regular expert involvement.
8,500 Operating Credits per month across one or two active lanes, standard+ agent access and light expert contribution. A short monthly guidance session and a written maintenance plan stay attached to the workspace, with a +15% burst window for urgent weeks.
Balanced progress across build and maintenance
For products and systems that need steady movement. Best for ongoing development, recurring improvements, AI workflows and integration work that needs clearer structure and more visible ownership.
18,000 Operating Credits per month across two active lanes, advanced agent access and balanced expert contribution. A named delivery owner holds the workspace, a monthly technical advisory session shapes the next cycle, and a +20% burst absorbs short surges.
Higher pressure, stronger oversight
For heavier product work, larger integration layers, more demanding maintenance and systems that need stronger control over priorities, delivery rhythm and review depth.
40,000 Operating Credits per month across three active lanes, premium agent access and strong expert contribution. A named delivery owner plus lead oversight run a biweekly operating rhythm with two guidance sessions per month and a +25% burst window.
Maximum standard capacity before dedicated programs
For active systems that need strong visibility, dense review, higher active capacity and a more mature operating rhythm without moving into a dedicated Ultra structure yet.
75,000 Operating Credits per month across four active lanes, premium+ agent access and deep expert contribution. A named delivery owner with structured lead oversight runs a weekly rhythm, priority queue handling and a +30% burst window.
Operating Credits are the shared capacity unit inside the Orzed Console. They can be used across agent work, expert contribution, technical implementation, maintenance actions, advisory tasks and urgent interventions. The same plan covers many types of work.
Some work types consume capacity faster than others. Custom design, advanced architecture, specialist engineering and high-stakes review use higher operating weight. Credit usage is visible live, so the rhythm stays honest: when a cycle leans heavy, the Console shows it before the month ends.
COMPARE CORE
All Core Plans use the same operating model. What changes is the available capacity, active work pressure, expert involvement and visibility depth inside the system.
| Feature | Touch | Pulse | Flow | Drive | Control |
|---|---|---|---|---|---|
| Monthly price | $900 | $1,900 | $3,900 | $7,500 | $12,900 |
| Annual price | $9,000 | $19,000 | $39,000 | $75,000 | $129,000 |
| Operating Credits per month | 4,000 | 8,500 | 18,000 | 40,000 | 75,000 |
| Weekly usage cap | 35% | 40% | 45% | 50% | 60% |
| Expert contribution depth | Light | Light+ | Balanced | Strong | Deep |
| Active work lanes | 1 | 1 to 2 | 2 | 3 | 4 |
| Agent tier access | Standard | Standard+ | Advanced | Premium | Premium+ |
| Emergency burst allowance | +10% | +15% | +20% | +25% | +30% |
| Delivery ownership | Shared | Assigned contact | Named owner | Named owner, lead oversight | Named owner, structured oversight |
| Advisory rhythm | Readout only | 1 short session | 1 technical advisory | 2 guidance sessions | Weekly operating review |
| Maintenance rhythm | Readout | Monthly plan | Monthly plan + improvement read | Structured maintenance | Continuous rhythm |
| Reporting depth | Basic | Standard | Detailed | Advanced | Management-level |
| Monthly credit carryover | 30% | 30% | 30% | 30% | 30% |
| Annual credit carryover | 50% | 50% | 50% | 50% | 50% |
INSIDE A CORE PLAN
Core Plans are not locked to one type of work. The same capacity moves across these categories as the cycle changes.
Routine maintenance and fixes
Stabilise what is in production without spinning up a new project.
Fresh startup builds
Get the first real version into users before the structure hardens.
AI-assisted workflows
Copilots, retrieval, automation triggers running under real review.
Product shaping and iteration
Small changes that keep the product moving between major releases.
Integrations and automations
Connecting systems that should never have stayed manual.
Technical guidance and review
Architecture, security and release calls that a solo team cannot hold.
Post-launch improvements
The quieter work that keeps a release healthy instead of drifting.
Urgent but limited interventions
Short, focused pressure when a week goes sideways.
ADD CAPACITY
Core Plans are built to stay flexible. If the work suddenly expands, capacity, specialist weight or urgency room can be added without replacing the plan that already holds your system.
Extra Agent Capacity
Raise agent throughput inside the same workspace when volume climbs.
Extra Expert Contribution
Attach more senior review weight to a cycle without moving up a plan.
Emergency Burst
Stretch the burst window for a single period of real pressure.
Design Intensive
Concentrated UI, product and brand design when a phase needs it.
Additional Technical Advisory
More architect and lead time for decisions that shape cost or risk.
Extra Work Lane
Open another parallel lane without reshaping the whole plan.
HOW IT BEHAVES
Six rules that define the operating contract. No surprises at month close, no surprises at renewal.
When one lane is not enough and release discipline matters as much as implementation speed. Denser execution with stronger oversight.
Explore Prime ↗ Company-wideAn embedded operating layer across strategy, systems, governance, AI adoption and continuity. Custom-designed around the business as a whole.
Request Enterprise access ↗You do not need to overbuy the structure on day one. Start with the Core Plan that fits your current work, then increase capacity only when the system asks for more.