Setup and subscription
Our FDEs bring Qurify into your company and carry out your AX transformation
Qurify is a subscription AX solution that automates office, sales, and other functional work with LLM-based agents. A dedicated Forward Deployed Engineer (FDE) brings Qurify into your company, sets it up in about a month, and then keeps building the agents you need. You choose between subscription (SaaS) and on-premise installation inside your company.
Who
Your FDE builds agents for the work you want covered
A dedicated FDE
The FDE who learns your work and data stays with you from setup through operation. FDEs are not stationed on site; they take the work you want covered and build agents for it. Handovers happen inside our team, so context is not lost when people change.
One point of contact
Our lead takes your teams' requests, sets priorities with them, and gets them done. You never juggle multiple contacts.
Progress measured in agents
At every stage you see which agents were added and what remains, on screen and in the record. Progress is judged by agents in use, not hours spent.
Steps
From first conversation to operation, in this order
- 01
Inquiry
Tell us one task you want solved and where the data lives; we reply within 2 business days.
What you confirm at this step
A consultation date - 02
Understand the work and the data
We confirm which reports and questions your teams repeat, where the data behind them lives, and your closed-network and security requirements.
What you confirm at this step
The first agent to add and the data to connect - 03
Setup (about a month)
The Ontology Agent pulls in data and builds the ontology while your FDE configures work agents. Once chat is ready, your teams start working by asking and answering.
What you confirm at this step
The first agent your teams use by chat - 04
Operate
As people work, the Assetization Agent builds up know-how as assets. Your FDE keeps adding agents for new work you want covered.
What you confirm at this step
New agents and accumulated assets
First month
How the first month of setup unfolds
Building the ontology and configuring agents run side by side. While the Ontology Agent ties the data together, your FDE takes your work and business requirements and configures multiple agents.
- 01
Connect data
Structured and unstructured data — RDBs, ERP, OneDrive — and chat data are connected where they already live.
- 02
Build the ontology
The Ontology Agent ties the connected data to the words your teams use.
- 03
Configure work agents
Your FDE configures office, sales, and other functional agents to your work and requirements.
- 04
Start using chat
Teams start working by asking and answering, checking the evidence behind each answer.
Setup time depends on how much data is connected and its condition. We settle it together after understanding your work and data.
Deliverables
Records that stay with you
These two stay with you, so business rules and their evidence can be checked again even when people change.
Business API specification
A document describing what each business rule takes in and what it returns.
Call log
A record of when each rule ran, on which data, and what answer it produced.
The business rules defined with your teams, and their specifications, belong to you.
Deployment
Two ways to adopt Qurify: subscription (SaaS) or on-premise
Qurify is not a system built once and handed over. Either way, your FDE keeps adding agents after setup. Companies with strict security requirements, such as finance and the public sector, adopt it on-premise.
Subscription (SaaS)
A monthly subscription after setup
- After about a month of setup, you move to a monthly subscription
- Base usage is set by company size; only usage above it is added
- FDEs are not stationed on site; they take the work you want covered and keep building agents for it
On-premise
Installed inside your company, so data does not leave it
- Installed on your own servers or inside a closed network with no external connection
- If external AI APIs are not allowed, Qurify runs on models hosted on your in-house GPU servers
- Pricing and base usage are explained in consultation after we understand your installation environment
For public-sector tenders, the contract form follows the agency's conditions.
Where the data stays
Your data stays where it is
Installed in your environment
Installed on your servers or in your cloud. We do not move your data to our side.
Runs on closed networks
Built and operated even on networks with no external connection. One system runs inside a public agency's building today.
Existing systems stay as they are
ERP, business databases, and document stores are connected without being changed.
Fit
Security conditions follow your environment
Security reviews, network separation, equipment restrictions — conditions differ by customer, so we confirm them first and install Qurify within them. The stricter the conditions, the longer the first conversation.
- Security review and network separation requirements are checked during discovery
- Data access is granted only within the scope you define
- The AI model is chosen for your environment; if external APIs are not allowed, an in-house model is used
Expand
Start with one task, then widen agents and connections
We do not connect all company data at once. We connect core business data first, then expand step by step — validating with your teams — to unstructured material such as documents and email, and to new work agents. Next, a Data Science Agent that runs advanced AI modeling on the ontology is planned for release.
Simpler is better
Even when the goal is company-wide coverage, the fastest and safest path starts at a low level with the core of your structured data. Each stage is verified and agreed with your team before promotion, reducing the risk of misdefined semantics propagating errors company-wide.
Five levels of data connection
L1
Structured Schema Mapping
Maps ERP tables and code systems to standard terminology. A fully predictable, easily auditable starting point.
L2
Standard Terms · Entity-Relationship Definition
Defines core entities and relationships, enabling automatic classification and duplicate detection for structured data.
L3
Unified Document and Data Connection
Extracts meaning from contracts, emails, and documents and links it to structured entities. This is where unstructured materials start serving as evidence for answers.
L4
Connection Proposals with Human Approval
The system proposes new entity and relationship candidates; humans approve or reject them. A stage requiring more sophisticated governance.
Research stage
L5
Goal-Driven Structure Composition
The system composes and reorganizes connection structures around a business goal. Currently theoretical and experimental.
Research stage
For most customers, the realistic target is L1–L3. Choosing the level that fits your purpose — not the highest level — is the most economical path.
What we confirm with your teams at each step
- 01
Propose
We present a draft of that level's semantic structure (entities, relationships, mapping rules) along with the rationale for the sequencing.
- 02
Verify
Your team checks the mappings against real data and business terminology, confirming they match how your organization actually works.
- 03
Adjust
Mismatches and edge cases are surfaced together and fixed immediately. This back-and-forth is what drives semantic accuracy up.
- 04
Agree & Freeze
The connection structure for that level is confirmed as the baseline, with every change recorded in an audit trail.
- 05
Promotion Decision
After weighing business value, risk, and organizational readiness, we decide together whether to move up a level (or stay where it makes sense).
Frequently asked questions
Q.How does it proceed?
We reply within 2 business days, understand your work and data, then set up for about a month. After setup you run it as a subscription or on-premise, and your FDE keeps adding agents for the work you want covered.
Q.How does pricing work?
It depends on how you adopt Qurify. Subscription (SaaS) is a monthly fee after setup; base usage is set by company size, and only usage above it is added. For on-premise, pricing and base usage are explained in consultation after we understand your installation environment.
Q.What is an FDE? Are they stationed on site?
A Forward Deployed Engineer is our dedicated engineer who brings Qurify into your company and builds agents for the work you want covered. FDEs are not stationed on site. Our lead takes your teams' requests and sets priorities, and the FDE builds them into agents.
Q.How long does setup take?
About a month. It depends on how much data is connected and its condition, so we settle scope and schedule together after understanding your work and data.
Q.What is the Assetization Agent?
An agent developed in-house by SmartMind AI. As each user works through conversations under the permission model, it turns their know-how into assets automatically and keeps refining them with a Self Improvement assetization algorithm. The best personal assets are promoted to global assets and rolled out company-wide.
Q.Where does the data live?
Qurify is installed on your servers or in your cloud, and the data stays where it is. It also runs on closed networks with no external connection.
Q.Do we have to change existing systems?
No. ERP, business databases, and document stores stay as they are; only the data you need is connected. Several systems can be connected at once so answers appear on one screen.
Q.Do you take on public-sector tenders?
Yes. One system runs inside a public agency's building today, and we take part in tender-based projects. The contract form follows the agency's conditions.
Let's decide which work gets an agent first
One task you want solved and where the data lives is enough to start.