First we define what it has to do.
Then we define what it costs.
Every architecture is configured according to the processes, actions and integrations your business needs. Before starting, we define the scope and the investment together with you.
You don't pay for hours, tokens, or prompts.
You pay for a system implemented inside your business: the architecture that sustains it, its configuration, the integrations, the actions it executes, the testing, and the launch — and afterward, for keeping it running.
The investment has three parts.
The work needed to design, configure, connect, test, and launch the system.
Keeps the already-built system operational and up to date according to the contracted scope.
Telephony, infrastructure, Meta/WhatsApp, AI models, APIs, or other providers can have their own costs. They're identified before implementation.
Need a reference before talking to us?
Some simple CONNECT or VOICE configurations can start at €79/month.
This reference doesn't apply to the starting price of every system. SALES, OPS, SYSTEMS, WEB, and combined architectures are valued according to their scope.
The initial implementation is quoted separately.
Scope isn't a figure. It's a set of decisions.
The same product can be two very different systems.
- Answer
- Inform
- Transfer
- Identify customer
- Check CRM
- Check calendar
- Book
- Confirm
- Log
Both use VOICE. But they don't require the same architecture. That's why scope is defined before the quote.
We don't charge you every time your business changes.
If prices, hours, promotions or information change, or the operation we already built needs a reasonable adjustment, that can be part of the monthly fee, depending on the contracted scope. We only quote a new implementation when something important that didn't exist before needs to be built.
One system, one scope, its own configuration.
Each agentic solution is configured around what your business needs it to do: its channels, its actions, and its integrations. That's why there's no single price per product — scope is defined with you before quoting.
Real calls — answers, books, transfers, and works after hours.
Telephony and voice provider usage not included.
Conversations on web and WhatsApp — understands, checks, and acts.
Qualifies, classifies, and follows up on every lead before it goes cold.
Automates internal processes: interprets, extracts, classifies, and notifies.
Custom software, valued based on what we build.
Each tier describes the system's scale — users, permissions, integrations, data and architecture complexity — not a fixed price package. The figure comes from a technical assessment, not a table.
Dashboards, internal tools, simple portals and delimited systems.
CRM, business portals, operational applications with users and permissions.
Platforms, vertical software and complex digital products.
Voice + Connect + Sales + Ops + Systems combined in a single architecture, integrated with your own data and departments. Custom implementation, monthly fee based on architecture.
The digital infrastructure that supports your systems.
Implementation based on scope. WEB belongs to your business's digital infrastructure, not the agentic solutions — it has its own pricing logic, valued according to the level you need.
A high-impact single page to launch fast: pitch, social proof and CTA.
Several pages, more content depth and real business structure.
Full architecture ready to grow and integrate with your systems.
Catalog, cart and checkout — ready to connect with Connect, Sales and Ops.
When WEB is part of an architecture with another active STEAMNODE system, its monthly fee can follow a different logic — explained when valuing the project.
Not every project needs the same thing.
Below is what can be included — the exact scope of each project is defined before quoting, according to what your system needs.
- Technical discovery
- Architecture design
- Configuration
- Development
- Integration
- Testing
- Launch
- Initial personality, knowledge, and rules configuration
- Basic operating documentation, when applicable
According to the contracted scope
- Maintenance of the existing system
- Support
- Fixes
- Information updates
- Reasonable rule adjustments
- Maintenance of existing integrations
- Small evolutions of what's already built
- A new application
- A new CRM
- An important new integration
- A new module
- A different architecture
- A full second system
That gets quoted as a new implementation
- Change business hours
- Update prices
- Adjust a response
- Add a new FAQ
- Change an existing rule
- Build a customer portal
- Connect a new ERP
- Add a full CRM
- Create a new module
- Build a new application
Some costs aren't STEAMNODE's.
Some architectures need external services to work. These services are paid separately when the project needs them — they're not part of STEAMNODE's implementation or monthly fee.
Whenever possible, the account can be set up directly under the client's name.
Operating VOICE does not mean unlimited calls. Telephony consumption and voice provider costs are not included and are billed separately.
When several systems are part of the same architecture, we value the whole — not an endless stack of subscriptions.
If you combine STEAMNODE products, we evaluate the complete system before quoting. That can mean different entry pricing than simply adding up each product separately, depending on how they integrate with each other.
Here's how we go from your problem to the final price.
- 01Understand
What happens today.
- 02Define
What the system should do.
- 03Design
The architecture.
- 04Propose
Scope and investment.
You'll know what we're going to build and how much it costs before we start.
Request a quotePrices subject to applicable taxes where relevant.
Not sure which system your case needs?
You don't need to pick a product. Tell us what you want to solve and we'll define the architecture before quoting.
What's usually asked before valuing a project.
Do all systems start at €79/month?
No. Some simple CONNECT or VOICE configurations can start at €79/month. Other products and architectures are valued according to their scope.
Is there an initial implementation?
Yes. Its cost depends on what we need to design, configure, integrate, and deploy.
Why don't you publish a price for each product?
Because the same product can do very different work within two companies. We first define what it must do, then quote its architecture.
What does the monthly fee include?
Depending on the contracted scope, it can include maintenance, support, fixes, information updates, reasonable adjustments, maintenance of existing integrations, and small evolutions.
When does something need a new implementation?
When we need to build an important module or feature, a substantial new integration, a different architecture, or a new system.
Are there third-party costs?
Yes, when the architecture needs external services — telephony, Meta/WhatsApp, AI models or other APIs. They're identified before implementation.
Can I start with something small?
Yes, when the problem can be solved in a bounded way. The goal is to build only what makes sense for your current case and grow from there when needed.