mia
mia is a decision intelligence platform from Amsterdam-based AureliaX Consulting that merges customer, competitor and market signals into ranked, source-cited opportunities and next actions for product, growth and go-to-market teams, deployed inside the customer's own Azure tenant.
What is mia?
mia is a decision intelligence platform published by AureliaX Consulting B.V., a company based in Amsterdam. The problem it addresses is stated plainly on the site: customer feedback, market movements and competitor activity sit in separate tools, and by the time a team has connected the dots the window to act has closed. Rather than adding another dashboard or chatbot, mia positions itself as a layer above the systems a company already runs, turning their data into ranked decisions. The platform is organised into four modules. Voice of Customer unifies reviews, support conversations, sales calls and social signals, surfacing themes, sentiment and churn risk. Competitor Watch follows rivals in real time and raises alerts on launches, pricing, positioning, partnerships, hiring and messaging changes. Market Radar covers trends, regulations and white space by geography. Opportunity Intelligence combines those signals into ranked opportunities and risks with a recommended next action per business unit. The processing chain runs in three stages: continuous signal collection, an intelligence layer that produces structured and sourced summaries, and a decision layer aimed at product, go-to-market, strategy and operations. An anti-hallucination pipeline retrieves and scores sources on freshness, authority and relevance, checks each claim against them, then rewrites, removes or re-grounds whatever fails. mia is model-agnostic (Azure OpenAI, Microsoft Phi, Anthropic on Azure or self-hosted open models) and switching model is presented as a configuration change. More than 50 connectors across nine categories feed it, with a webhook and REST layer for the rest, and output reaches users through Slack, email, a dashboard, an API and exportable reports. Deployment defaults to the customer's own Azure tenant, with private cloud, full on-premise and a publisher-managed option also offered. The publisher describes an early stage: design partners and a first cohort, a mia for Enterprise launch on 1 July 2026 and press coverage in January 2026. The impact figures shown on the site (+35% close rate, 30-50% faster go-to-market, 97% faster insights, 5x faster decisions) and the companies named on the about page are publisher claims, not measured results or contractual references. The publisher also states that mia takes no autonomous decisions: every output is a draft until a person approves it.
What it does
- Unify reviews, support tickets, sales calls and social signals into a single view of the customer
- Track competitors in real time: launches, pricing moves, positioning and narrative changes
- Rank opportunities and risks, and recommend the next action per account, deal and business unit
- Monitor market trends, regulations and white space by geography
- Produce battle cards, voice-of-customer analyses, executive briefings, opportunity reports and trend analyses
- Push signals and decisions into Slack, Jira, Linear, HubSpot, Salesforce, Notion and the BI stack
- Attach a source to every insight and drop claims that cannot be evidenced
When to use mia / When not to
A quick filter to help you decide if mia is the right fit.
When to use mia
- Product, growth and go-to-market teams that follow several competitors and need to react quickly to launches, pricing moves or positioning shifts.
- Organisations with data sovereignty requirements: mia is deployed by default inside the customer's own Azure tenant, with customer-managed keys and European data residency.
- Small and mid-sized companies that need customer and competitive intelligence but have no dedicated in-house intelligence team.
- Large accounts operating across several markets and product lines, looking for one decision layer over signals scattered across tools.
- Teams already running Salesforce, HubSpot, Gong and Slack, and buyers who require every insight to be traceable back to its source.
When not to use mia
- Buyers who need a published price: there is no rate card, no tier and no range, so every purchase goes through a sales quote.
- Anyone expecting self-service sign-up or an instant free tier; the only entry point on the site is a booked demo.
- Teams looking to replace their CRM or BI stack, or expecting autonomous decisions: mia sits on top of existing systems and treats every output as a draft until a person approves it.
- Organisations outside the Microsoft ecosystem, since the default deployment runs in the customer's Azure tenant with Entra ID, and no mobile app or browser extension exists.
- Teams that need a non-English interface, or that require a long-established vendor: the domain was registered in July 2025 and the Dutch register lists a single employee.
How to use mia
A typical end-to-end flow, from setup to results.
- Book a 15-minute demo from the contact page; there is no self-service sign-up anywhere on the site
- The publisher prepares an intelligence snapshot ahead of that call
- Receive a tailored quote and a short ROI model, promised within one business day
- Request the free trial, which the terms describe as available on demand and without a credit card
- Run a guided pilot on a portion of the pipeline to measure close rate and cycle length before committing
- Choose the deployment mode: the customer's own Azure tenant by default (subscription, Entra ID, storage and billing), or a publisher-managed option
- Connect the standard sources - Salesforce, HubSpot, Gong, Slack and the data warehouse - which the publisher says work out of the box
- Configure identity: Microsoft Entra ID, Okta or any SAML 2.0 provider, with SCIM 2.0 provisioning, conditional access and fine-grained permissions
- Go live: most teams are said to reach production in under two weeks, with dedicated onboarding and ongoing model tuning included
- Use it day to day through custom playbooks, Slack and email alerts and digests, exportable reports and the API
Pros & Cons
Pros
- Traceability: every claim is tied to its source and passes a three-step verification pipeline before delivery
- Clear position on training: the publisher states that customer data is never used to train, fine-tune or evaluate any model
- Sovereignty and residency: deployment in the customer's own Azure tenant, customer-managed keys, an on-premise option, no environment shared between customers, and European hosting by default
- Model-agnostic architecture, so no lock-in to a single LLM and switching is a configuration change
- Broad and explicitly named integration coverage: more than 50 connectors across nine categories, plus webhook and REST
- Compliance material ready for a procurement review: DPA, subprocessor list, DPIA template, penetration test summary and architecture diagram
- Candid certification status, with ISO 27001 declared in progress rather than obtained, and a measured pilot plus a claimed sub-two-week go-live before commitment
Cons
- No public pricing at all: no amount, no tier and no range, so a budget cannot be framed without a sales conversation
- No permanent free plan and no self-service sign-up; the only entry point is a booked demo
- No certification held to date: ISO 27001 is still in audit, and the rest is claimed alignment (NIST AI RMF, ISO/IEC 42001) or posture inherited from Azure
- Very young publisher: domain registered on 26 July 2025, first Wayback capture on 20 August 2025, and one employee declared in the Dutch register
- Impact figures (+35%, 97%, 5x, 30-50%) are published without method, sample or date, and the animated homepage counters read zero in the page source
- The companies named on the about page appear as the employers of users rather than as contractual customers, with no case study to back them
- A single published email address covers legal, GDPR, DPO and press with no dedicated support channel, compliance documents are only released on request under NDA, and there is no public API documentation, no mobile app and no declared interface language other than English
Pricing & Plans
There is no free plan and no published price point. mia is sold under a single tier named Custom, quoted on request, with pricing based on the number of seats and the number of connected revenue systems. The publisher promises a quote and a short ROI model within one business day of first contact. Prices exclude VAT, and volume discounts and multi-year terms are stated to be available, without any published scale. Billing runs monthly or annually, chosen at subscription, with automatic renewal, 30 days' notice before any price change, and cancellation taking effect at the end of the current billing period. A free trial is available on request without a credit card, and a guided pilot on part of the pipeline can precede a full rollout. No lowest price point or currency can be reported, because no amount is published.
- the single published plan
- covering unlimited connectors to CRM
- product and conversation sources
- next-action recommendations for accounts and deals
- custom playbooks
- alerts and Slack or email digests
- SSO
- SCIM
- entry mechanisms rather than priced tiers
- with no free or self-service tier published
Data, GDPR & hosting
A consolidated view of how mia handles your data.
GDPR overview
A dedicated GDPR page, last updated in May 2026, sets out the publisher's compliance and restates the seven GDPR principles. Seven data subject rights are listed (access, rectification, erasure, restriction, portability, objection, automated decision-making), with consent withdrawal added in the privacy policy; all are exercised at hello@gomia.ai, the same address given for the data protection officer. Processing takes place mainly in the EEA, and transfers outside it rely on standard contractual clauses. Breaches are notified within 72 hours. A DPA, a subprocessor list and a DPIA template are available on request; the terms also reference CCPA. AureliaX Consulting B.V. is established in the Netherlands, so no Article 27 representative is required. Alignment is claimed with the EU AI Act, NIST AI RMF and ISO/IEC 42001, while ISO 27001 is in progress, with an audit scheduled rather than obtained.
Who owns the data?
The terms of service (section 5) state that the customer retains all rights to its data. AureliaX Consulting B.V., the controller registered under KVK 97362263, grants itself only a limited licence: processing and analysis needed to deliver the service, aggregated and anonymised insights used to improve it, and storage and backup. The security page states that data stays in the customer's own environment, since mia is installed in the customer's Azure subscription with storage billed to the customer, and that no index, cache or memory is shared between customers. The publisher declares it does not sell personal data, and that a departing customer's environment is theirs to delete.
Reuse rights
Customer content remains the customer's own to reuse, export and delete without asking permission; the publisher processes it only to deliver the service. The privacy policy lists the purposes: providing and improving the platform, handling transactions and subscriptions, service communications, usage analytics, security and fraud prevention, and legal obligations. The categories collected are account data (name, email, company, role), usage data, technical data (IP, browser, device, cookies), payment data and communications. The legal bases given are contract performance, legitimate interest, consent for optional marketing and cookies, and legal obligation; essential cookies run without consent while analytics and marketing cookies require it. On model training the position is explicit: customer data is never used to train, fine-tune or evaluate any model, and prompts and documents stay inside the customer's environment. Only aggregated, anonymised insights may be reused by the publisher to improve the service.
Data retention & training
Hosting summary
Data is hosted in Europe by default: Microsoft Azure West Europe (Amsterdam) or North Europe (Dublin), with optional OVHcloud regions in France, described as aligned with Trusted Cloud and SecNumCloud, for stricter EU residency. The default deployment installs mia inside the customer's own Azure tenant, so storage, compute and network stay under the customer's control, with keys held in the customer's Azure Key Vault and rotation and revocation in the customer's hands. No environment is shared between customers: no common index, cache or memory. Data is encrypted in transit and at rest, and the privacy policy describes the infrastructure as ISO 27001 aligned rather than certified. Processing takes place mainly in the EEA; transfers outside it rely on standard contractual clauses. The infrastructure is presented as multi-zone AKS with stateless services, continuous backups and snapshots every 12 hours, with recovery tested quarterly. The named hosting subprocessors are Microsoft Azure and OVHcloud. Note that the domain's public IP answers from a Cloudflare anycast node geolocated in Poland: that is the CDN, not where data lives.
Things to keep in mind
Risks and trade-offs to weigh before adopting mia.
- No published price means a budget cannot be estimated without going through sales, and comparison with other tools is impossible before that conversation.
- ISO 27001 is not held: it is stated as in progress with an audit scheduled. The HIPAA and FedRAMP posture cited is Azure's, inherited through tenant deployment, not a certification of the publisher.
- The DPA, subprocessor list, DPIA template and penetration test summary are supplied only on request, with an NDA option, so nothing is publicly verifiable beforehand.
- The impact figures (+35%, 97%, 5x, 30-50%) carry no method, sample or date, and the companies named on the about page are presented as the employers of users, not as contractual customers: both are publisher claims.
- Over-reliance is a genuine risk. The platform ranks opportunities and recommends next actions, and the publisher itself treats every output as a draft pending human approval; a team that stops questioning the ranking hands its judgement to a summarisation layer.
- The publisher was registered recently and is very small, with one employee declared, so service continuity is worth checking before a multi-year commitment. A single email address covers legal, GDPR, DPO and support needs, and the press contact sits on a separate domain (aureliax.co).
- No minimum age is stated in the terms or the privacy policy, and the responding IP address geolocates to Poland, which is a Cloudflare anycast node and says nothing about where data is stored.
Setup & Integrations
Technical difficulty
Moderate, and it depends on the deployment mode. The publisher says most teams reach production in under two weeks, with Salesforce, HubSpot, Gong, Slack and data warehouse connectors working out of the box, and dedicated onboarding included. The default deployment installs mia in the customer's own Azure tenant, which assumes a cloud or IT team with rights over the subscription, SSO and SCIM configuration (Entra ID, Okta or SAML 2.0) and key management in Key Vault. A full on-premise option is heavier; a publisher-managed option removes most of it. There is no self-service setup.
Deployment
Integrations
Behind mia
Social
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
What does mia actually do?
How long does it take to go live?
Is customer data used to train models?
Where is the data hosted?
Can mia run in our own Azure tenant?
Does mia replace our CRM or BI tools?
How is pricing structured?
Can we try it before committing?
Which certifications does mia hold?
Does mia make autonomous decisions?
Should you pick mia?
mia is a coherent product with unusually well documented governance for a company of its age. Deployment inside the customer's own Azure tenant, customer-managed keys, an explicit refusal to train models on customer data, a source attached to every insight and a ready-made compliance pack all point to a vendor built for procurement review rather than for viral adoption. The counterweight is just as clear. Pricing is entirely opaque: one plan named Custom, quoted on request, with no amount, tier or range published anywhere. The publisher is very young, the domain having been registered in July 2025 and the Dutch commercial register listing a single employee, which matters when a multi-year commitment is on the table. No certification is held today: ISO 27001 is in audit and everything else is claimed alignment or posture inherited from Azure. The impact numbers displayed on the site come with no method, sample or date, and the companies named on the about page are described as the employers of users rather than as contractual customers. The natural audience is a go-to-market or product team already running on Azure, with an enterprise budget and a real need for sourced, traceable intelligence rather than another dashboard. For a team that needs to compare prices before speaking to a salesperson, or that works outside the Microsoft ecosystem, the fit is weaker. The practical route is the booked demo followed by the measured pilot, and a close look at the compliance pack, before any commitment is signed.
- Choosing a selection results in a full page refresh.
- Opens in a new window.