Discovery / technical review
A short phase to understand the process, architecture, integrations and a sensible first-version scope.
Best for new products, complex automation and work with unknown technical risks.
Skip to contentASH Platform 01 02 03 01 02 03 04 05 06 AI / 01 AI / 02 AI / 03
TRANSPARENT ESTIMATION
SCOPE BEFORE PRICEThe scope sets the price. Not a flashy calculator.
Two projects both called a ‘website’ can differ several-fold in effort. We first define the problem, data, integrations and the boundaries of version one, then provide a price.
We do not publish a fictional ‘starting at’ number. After a short review, you get an estimate with explicit assumptions and a defined scope.
ASH STUDIO ≠ ASH PLATFORM
This page applies to custom ASH Studio projects. ASH Platform is a separate subscription product. Commercial Platform pricing will be published separately after approval.
ENGAGEMENT MODELS
The format depends on how much is already known.
Fixed scope
We define a concrete outcome, boundaries, milestones and price before implementation begins.
Works well for websites, redesigns and features whose requirements are sufficiently clear upfront.
Iterative development
We deliver working stages and revisit priorities after each reviewable result.
For web products and internal systems that evolve together with the business.
WHAT DRIVES COST
System behaviour matters more than page count.
Logic & roles
Authentication, permissions, portals, states, approvals and non-standard business rules.
Data
Data modelling, migrations, search, history, files and integrity requirements.
Integrations
CRM, Telegram, payments, external APIs, webhooks, retries and third-party limits.
AI / automation
Number of workflows, models, validation, human review and usage controls.
Design & content
Whether the project needs a new visual system, complex UI, illustration, copy or localization.
Reliability
Observability, audit, security, recovery and requirements around critical operations.
HOW AI COST IS STRUCTURED
Implementation, support and usage are different parts of the budget.
We do not publish a fictional fixed price for an AI Receptionist or Custom Agent. The workflow, integrations and expected usage come first.
Implementation / setup
Discovery, behavior design, knowledge, integrations, permissions, validation, QA and launch for the specific workflow.
A project cost shaped by the implementation scope.
Support / maintenance
Workflow changes, monitoring, knowledge updates, provider changes and ongoing improvement after launch.
Optional recurring support when the system needs it.
Provider usage
Model/API, messaging and other third-party costs depend on the providers selected and actual usage.
Estimated separately from architecture and expected volume.
BEFORE IMPLEMENTATION
You should know what you are paying for.
- 01
What is included in version one and what is intentionally outside it.
- 02
Which assumptions the estimate depends on and what could change the price.
- 03
Which milestones can be reviewed independently and what counts as done.
- 04
Which external services and recurring costs will remain after launch.
- 05
Who owns the code and data and how the product can evolve later.
FAQ / 03
Why is there no exact price list on the site?
Because we do not want to sell a fictional number. A landing page, a multilingual corporate site and a product with CRM can all be called a website, but they are different projects. Scope comes first, price comes second.
Can we start with a smaller version?
Yes. That is usually preferable: identify the smallest useful vertical slice, launch it, then expand only after seeing real usage.
Can you work within a limited budget?
Budget is an architectural constraint. If the whole problem does not fit, we can reduce scope, split the work into stages or use an existing product where custom development is not justified.
WANT A REALISTIC RANGE?
Give us context, not a perfect specification.
The form asks for a budget range, timing and project type. That is enough to start a practical scope discussion.
Get a scope estimate