Plan a complete budget for your application
Compare the initial setup, the recurring project subscription and the business areas included. Hosting is a separate part of the budget: confirm both the functional scope and the environment choices before committing to the project.
Level 1
A customer workspace and back office for your business application.
KSh 149,500
/month
Setup: KSh 1,359,020
Present your project- Customer workspace and back office
- Business areas included: 4
Level 2
The application, with a public showcase website that presents it.
KSh 225,000
/month
Setup: KSh 1,661,020
Present your project- Customer workspace and back office
- Business areas included: 5
- Public showcase website
Level 3
The application, with a dynamic public website.
KSh 300,500
/month
Setup: KSh 2,114,020
Present your project- Customer workspace and back office
- Business areas included: 6
- Dynamic public website
Level 4
The application, with a dynamic public website and website generation.
KSh 451,500
/month
Setup: KSh 2,869,030
Present your project- Customer workspace and back office
- Business areas included: 6
- Dynamic public website
- Website generation
Three decisions to make before confirming
- Define the first scope
- List the business areas needed for a useful first version, then the workflows and pages inside each one. For example, orders, customers and stock may be separate areas even when a single workflow crosses all three. Review this grouping against the offer’s included allowance.
- Choose the public surfaces
- A customer workspace and back office serve the application. The catalogue distinguishes plans with a showcase website, a dynamic website and website generation. Specify the public pages you need and check their inclusion rather than assuming that every surface is part of every plan.
- Account for operation
- Review production hosting, the location and the test environments you will use. Keep setup, subscription, additional scope and hosting visible as separate budget lines. Before paying, confirm the workspace recap, currency and payment terms for the selected project.
Read each amount in its own context
- Compare offers through the scope they cover
- Read the included business areas and the project conditions alongside installation and subscription. The offer should correspond to the application you intend to build. Use the project’s actual offer recap when confirming. The public plans introduce the structure; your project information states the applicable scope and recorded amounts.
- Make an extension a deliberate choice
- A new business area should answer a clear user need. Compare it with the areas already included before reviewing the proposed extension. This keeps a scope decision connected to its installation and subscription information. You can assess the change with the actual project offer rather than assuming every addition is already covered.
- Read hosting and invoices in their own context
- Hosting concerns the services running each environment. Review the associated usage and billing information to understand that part of the project’s operation. Project invoices retain their own description, date, amount and status. Keep those records separate in your reading so that each amount has an identifiable purpose.
Separate project scope from hosting costs
Setup covers the installation amount in the selected offer. The monthly price shown on each plan is the project subscription. Production hosting depends on its tier and location; development and staging are recorded according to their running time.
| Additional business areas | Project offer |
|---|---|
| Production hosting | Monthly |
| Development and staging | Running time |
A business area groups related workflows and can contain several pages. Additional areas and changes to the offer should be reviewed in the workspace before confirmation. The payment recap provides the charges and terms that apply to your project.
Match the offer to a real business workflow
Describe the people, data and actions that your application must support. Review the proposed business areas and environment choices before confirming the budget.
Understanding the offer and its costs
It is the recurring project subscription shown in the commercial catalogue. The setup amount appears separately on each plan. Production hosting, test-environment running time and additional scope must also be considered; the plan’s monthly figure is not a total hosting-inclusive budget.
Count groups of related business work, not individual screens. An order area could include a list, an order record and associated actions. The project’s confirmed scope determines the grouping; compare the areas in that scope with the allowance before adding more.
The catalogue distinguishes a public showcase website, a dynamic public website and website generation. Choose according to the role of the public site and confirm the pages and behaviours in the offer. These labels alone do not define every content-management or integration requirement.
The onboarding and payment recap present the startup payment and any remaining installation charges. Check these amounts, their timing and the accepted scope before paying. The public setup amount does not replace the project’s payment recap.
Use the project’s offer and roadmap to review additional business areas or a different scope. Distinguish a change within an existing workflow from an extension of the project. Confirm any effect on the offer and hosting before treating the extension as included.
Public prices follow the currency of the selected country using the platform’s pricing conversion. Check the country selector and the payment recap when comparing amounts. The recap remains the reference for the currency, charges and terms you are confirming.