1
Define the business goal
Start with the outcome: company presence, product sales, bookings, or internal operations. A clear goal saves cost and time.
Client knowledge center
Start your software project with clarity
A simple guide for non-technical clients: what to prepare, how to compare packages, and what happens after submitting the order — locally or internationally.
2
Pick a level or project type
Compare packages if you know the level, or choose “I don’t know”, then pick the project type (website, app, store…) and sub-requirements.
3
Prepare your core files
Logo, brand assets, service copy, photos, page content, and references help the team start quickly.
4
Send the request and transfer proof
After choosing a package, submit the order and upload the bank transfer proof for admin review and documents.
5
Track project status
Your account shows the current phase, latest update, what is needed from you, and related files or documents.
What should I prepare before ordering?
- Logo or clear business name
- Official phone and email
- Core page content
- Photos or design references if available
- Billing details and address
- Transfer proof when submitting the order
Helpful guides
Practical knowledge articles
Short, practical notes about packages, services, sub-requirements, and estimates — without technical jargon.
Files to prepare before starting
A practical checklist for logos, content, images, and design references.
Useful files
- Logo or brand assets if available.
- Business name and official contact details.
- Page content or a short description for each page.
- Product, team, or location photos when relevant.
- Design references or links you like.
How to write your project scenario
A simple way to describe goals, pages, users, and expected flows in text or Markdown.
Suggested format
Start with the business goal, then list pages or screens, then explain what the customer should do.
What happens after submitting an order?
A simple explanation of review, approval, project status, and later file uploads.
After submission
Admin reviews the request and proof of transfer, then approves it or asks for more information. After approval, project status appears in your account.
How to choose the right service level (package)
A simple guide to Basic, Professional, Advanced, VIP, and Enterprise levels — and when to choose “I don’t know”.
What is a service level?
Service levels — packages — describe project size and delivery expectations: pages or screens, admin tools, support, and typical features.
Levels on the site
| Level | Best for | | --- | --- | | Basic | A clear first launch: company site or simple v1 | | Professional | Richer content and experience | | Advanced | Broader platform with admin and operations | | VIP | Premium attention to detail | | Enterprise | Larger systems or corporate needs |
Tip: use package comparison — you do not need to memorise every difference.
When to pick a specific package
- You roughly know what you need (e.g. website + admin dashboard).
- The displayed package price fits your initial budget.
- The package features match what your team described internally.
What does “I don’t know — help me choose the right level” mean?
This is not a fixed-price package. It lets you:
- Pick the project type (website, app, store…).
- Set sub-requirements under each service.
- See a non-binding indicative estimate.
- Submit the request so the team recommends the right level after review.
Note: the package is optional on the order page. You can start with services first.
Next step: review package comparison or start your service request when ready.
What are services and project types?
Services represent the project type: website, store, app, admin system… and how to pick them on the order page.
Service = project type
On the order page, services are project types, such as:
- Website or web experience
- E-commerce store
- iOS or Android app
- Admin dashboard or internal system
- Integrations or automation
- Maintenance or later development
Browse services for a full description before ordering.
How to select a service
- Pick a service level if you know it, or choose “I don’t know”.
- Click the card that matches your project.
- Review sub-requirements under the service and customise what you need.
- You may select more than one service when the project combines types.
Note: with a specific level selected, only linked services may appear. Change the level or choose “I don’t know” to see every service.
Price shown next to a service
The figure is indicative for that project type — not the final project price. The final amount is confirmed after scope review and the agreement.
Next step: review package comparison or start your service request when ready.
Sub-requirements: included, add-on, or reviewed later
When you pick a service, items like payments, WhatsApp, or admin appear — this guide explains each badge.
What are sub-requirements?
After selecting a service (e.g. website or store), a list appears under it — not a flat list elsewhere — covering scope details: online payments, WhatsApp, login, reports, maps, notifications, external integrations, and more.
Click “Customize service requirements” to open and adjust your choices.
Three clear groups
| Badge | Meaning | What to do | | --- | --- | --- | | Included in the base price | Part of the default service scope | Keep or remove — removing does not lower the base price | | Optional add-ons | Extra capability with an indicative price when available | Enable only what you need | | Needs review | No price yet | Priced after scope review — not added to the numeric estimate |
Example: for a store, “shopping cart” may be included, a specific payment gateway may be an add-on, and “internal ERP link” may need review.
Why grouped under each service?
Each project type has different needs. A brochure site is not a full store. Grouping keeps the form relevant to your project.
Link to the indicative estimate
- Included: not counted as a separate add-on line.
- Selected paid add-ons: summed when a numeric price exists.
- Needs review: warning only — excluded from the figure until the team reviews.
Next step: review package comparison or start your service request when ready.
Package features: what “included in the price” means
Difference between package features on packages/order pages and sub-requirements under each service.
Package features ≠ sub-requirements
Two helpful layers on the site:
- Package features: shown when you pick a level on packages or order. They describe the typical delivery level (pages, support, admin tools…).
- Sub-requirements: appear under each service and customise that project type.
In short: the package answers “which level?” — sub-requirements answer “what details inside the project type?”
How package prices are shown
| Display | Meaning | | --- | --- | | Fixed price | You can order and pay through the usual flow after approval | | Starting from | Advertised minimum — estimate starts there + selected add-ons | | Priced to requirements | No number now — submit a quote request |
“Included features” in practice
- Fixed-price package: listed features are part of the offer; final scope is in the agreement after approval.
- “Starting from” or custom: features are typical for the level; final scope follows request review.
You do not need to understand every line item. Describe your goal — the team maps package, services, and requirements during review.
Before you order
Compare packages, then on the order page ensure selected services fit the level — or choose “I don’t know” for guidance.
Next step: review package comparison or start your service request when ready.
Indicative estimate: client guide
When the estimate appears, what it includes, and why it is non-binding with no instant payment.
What is the indicative estimate?
A helper figure on the order page showing cost direction before you submit. It is non-binding — no invoice and no payment now.
Remember: the final price is set after scope review and contract approval.
When does it appear?
1) “I don’t know” path
When picking services without a fixed level, the estimate adds:
- Visible numeric service prices only
- Selected optional add-ons with a price
- Excludes items marked “needs review”
2) “Starting from” or custom package
The estimate combines:
- Package starting minimum (if any)
- Selected service add-ons
- A warning when items are reviewed later
What is inside?
| Line | Meaning | | --- | --- | | Minimum / service base | Starting point for your path | | Selected add-ons | Only enabled items with a visible price | | Estimated VAT | 10% VAT per platform settings | | Total | Indicative — not the payment amount |
What it does NOT do
- It does not replace the official quote or invoice.
- It does not lock a price before admin review.
- It does not cover every complex item — especially “reviewed later” lines.
Mobile and desktop
On mobile you see a compact bar at the bottom; on desktop a side helper — open or close details without changing your selections.
Next step: review package comparison or start your service request when ready.
How to use package comparison before ordering
Practical steps to read the comparison table and link it to services on the order page.
Why compare?
Package comparison puts all levels in one table so you see differences without jumping between pages.
What you compare
- Price or pricing style (fixed / starting from / to requirements)
- Typical features per level
- Best fit (launch, growth, enterprise…)
Note: comparison shows the overall level. Fine details (payments, WhatsApp…) appear later as sub-requirements under each service on order.
Suggested steps
- Open comparison and pick a close level.
- Go to order and select the same level — or “I don’t know” if unsure.
- Choose the project type (service).
- Customise sub-requirements.
- Review the indicative estimate, then complete details and contract.
Still undecided?
Choose “I don’t know”, describe your project, and submit — the team recommends a level after reading your choices. You can also contact us before ordering.
Next step: review package comparison or start your service request when ready.