# Mindsmiths

Mindsmiths is the reliance layer for your customer stack. It sits on top of the systems you already run, such as CRM, billing, support and your app, next to your service AI and marketing tools. Every day, for every customer, it decides what would actually earn their trust: sometimes a message, sometimes a heads-up, often nothing at all. Over time more of your customers read you, answer you and come to you first, and that shows up where you're measured: acquisition, retention and growth.

Your team runs it, and running it doesn't take an engineer. It starts with playbooks already proven with other clients, your best people add what they know, and every change is tested against a group that doesn't get it. What helps stays. What doesn't gets dropped.

Our clients include national telecom operators, fintechs and an airport, in Europe and the US. Mindsmiths, Inc. is a US company.

**To see it running on one of your use cases,** write to Jordan Yates, our VP of Sales, at [jordan@mindsmiths.com](mailto:jordan@mindsmiths.com). [FILL, Jordan: booking link, 30 minutes.]

This file is the whole website. It's written so your AI can read all of it, and so can you.

## What it fixes

Most customers hear from a company when it wants something: an offer, a renewal, a review. They learn the pattern. They open less every year and check the price before they buy.

Every tool a company owns is built around one number. The app pushes the offer. The campaign tool sends the promotion. The loyalty programme rewards the purchase. The service AI closes the ticket. Each one does its job well. None of them works on whether the customer would choose you again without being asked.

That gap shows up in places every company already pays for:

- **Acquisition.** Most visitors leave without a word, and the cost of each lead goes up every year.
- **The first months.** Early cancellations, returns and support calls from customers who never got the product working.
- **Retention.** Customers go quiet long before they leave, and the first sign is often the cancellation.
- **Staff.** It takes months before a new hire sells like the best person on the team, and when the best person leaves, what they knew leaves with them.
- **Decisions.** What customers actually think reaches the people who decide weeks late, and smoothed over.

None of this shows up as one line in a budget, so it rarely gets fixed. It gets paid for every year instead, in ad spend, discounts and hiring.

## How it's different

Most AI that talks to customers does one of two jobs. Customer service AI answers what people ask. Marketing tools send what the company wants to sell. You keep both.

Ours does a third job: it works out what would actually help each person, and when. Sometimes that's a heads-up before something runs out. Sometimes it's weeks of help before any offer. Most days it leaves them alone.

That's how the people we rely on work: the mechanic who says the repair can wait, the doctor who says you don't need the scan. You go back to them for everything else.

### Where it sits next to what you already run

- **Your CRM, billing and data platform** keep the record. It reads from them and writes back what it did. Nothing is migrated.
- **Your decisioning engine** picks the best offer from your catalogue for the people most likely to take it. Ours decides something earlier: whether to reach this person at all, with what, and when. Often that isn't an offer. When it is, the offer is still yours.
- **Your campaign tool** sends what you plan to send. Contact rules, such as how often someone may hear from you, when, and who is left out, are hard rules in the system, not instructions to the AI. When your systems tell it who already heard from you this week, it holds back.
- **Your service AI** answers when customers ask. Ours is the one that notices before they ask.

It adds a job to your stack, not a system to replace. If you stop, nothing else has to change.

### Why not build it on a general model?

You can, and the messages will read well. The hard part is knowing which message, to whom, and when, and that comes from your best people and from testing on real customers, not from the model. That's the part we bring.

### How to judge anyone selling you this

Whoever you talk to, including us, these questions separate a pilot that proves something from one that only looks busy:

1. **Is the success number fixed before launch, on a number you already track, against a group that doesn't get it?** If results are reported only after the fact, they will always look good.
2. **Who approves what it says, and how fast can you switch it off?** The answer should be your team, and immediately.
3. **What does it do when someone is upset, overwhelmed or in crisis?** A system that only knows how to sell will keep selling.
4. **Does it run alongside the tools you already have?** You shouldn't have to replace anything to find out whether it works.

## What it does

Which plan fits. What to say to an upset customer. What changed this week, and why. Our AI helps with these small decisions, and checks afterwards whether it actually helped. The same layer works for your customers, your staff and your managers, each with its own voice. Each use case below is measured on a number you already track, and each is a place to start. One contract and one meter cover all of them: credits are pooled across your projects, so each business unit can run its own use case against its own number.

### For your customers

- **Finding you (acquisition).** Visitors get a real answer, with the reasons, before anyone asks for their number. *Moves:* leads from the same traffic, cost per lead. *Usually owned by:* marketing or growth. *Setup:* one line of code on your website; live within weeks.
- **Choosing well (conversion).** It recommends what fits and says why, including what they can skip. *Moves:* conversion, returns, early cancellations. *Usually owned by:* sales or e-commerce. *Setup:* [FILL, Juraj: typical time and systems needed.]
- **Getting started (onboarding).** One step at a time, when they need it, until the product works for them. *Moves:* early churn, support calls. *Usually owned by:* customer experience. *Setup:* connects to the systems where your customer data lives, so it takes longer. [FILL, Juraj: typical range.]
- **Staying (retention).** A heads-up before something goes wrong, and quiet the rest of the time, so they still read you when it counts. *Moves:* churn, response rate, usage. *Usually owned by:* customer experience or retention. *Setup:* connects to your customer systems, so it takes longer. [FILL, Juraj: typical range.]
- **Coming back (win-back).** For people who went quiet: weeks of something useful first, the offer last. *Moves:* accepted offers, cost per reactivation. *Usually owned by:* marketing or CRM. *Setup:* [FILL, Juraj.]

### For your staff

- **Daily coaching.** A few minutes a day of practice on the conversations people avoid, not the easy ones. *Moves:* conversion per person, time to ramp, attrition. *Usually owned by:* sales leadership or HR. *Setup:* quick; live within weeks.
- **Field sales.** Every morning: where to go, and which accounts are slipping before the quarter shows it. *Moves:* target attainment, accounts lost. *Usually owned by:* sales leadership. *Setup:* [FILL, Juraj.]

### For your managers

- **The weekly picture.** What customers said this week in their own words, including what nobody wants to hear, and an AI to ask the next question. *Moves:* days from a customer signal to a decision. *Usually owned by:* leadership. *Setup:* [FILL, Juraj.]

### How it works

1. **Notices.** It reads what is happening for each person from the systems a company already runs, such as billing, support and usage.
2. **Decides.** It works out whether anything would help right now. Often the answer is to do nothing.
3. **Helps.** It explains, reminds or answers on the channel the person already uses. When a person would be better placed to help, it hands over.
4. **Checks.** It looks at what happened next. What helped is kept, and what didn't is dropped.

## Proof

### Results so far

Measured in FMCG, telecom and financial services:

- **39% over yearly plan.** An FMCG field sales force, coached daily for two years, on one product line.
- **$4.62 in, $68.83 out, per user.** Financial services: about $15 back for every dollar. This compares engaged with never-engaged users; it was not a randomized test.
- **4.5x more accepted offers.** Same offer, same customers. Ours came after six weeks of useful notes.

### Talk to a client

Our clients take reference calls, in the US and in Europe. Jordan arranges them once we know which use case you're considering. Case studies naming them, with what changed and how it was measured, will appear here as each client approves. [FILL, Jordan: name the reference clients here once each gives written approval.]

### Who's behind us

Our seed round was led by Feels Good Capital, a venture firm that invests only in companies with a positive social impact. They made impact one of our main KPIs. The protocols under **When it gets hard** are how we hold to it.

## Working with us

### How you start

- It starts with one audience and one group of people, measured against a control group that doesn't get it.
- Your team approves every playbook before it goes live.
- We agree the success number before launch, on a number you already track.
- How long setup takes depends on what it touches. Helping visitors on your website takes one line of code, and short daily lessons for staff are just as quick: both can be live in about two weeks. Keeping customers longer means connecting to the systems where your customer data lives, so those projects take longer.
- It then runs for eight weeks against the control group, so you have a clear result inside a quarter.

### What you need on your side

Someone who owns the number, someone who knows your customers well enough to approve what the AI says, and access to the systems the use case touches. Some clients run it with one person, others with whole teams; it depends on the use case and what it connects to. We handle setup, integration and training for your team.

### What it costs

Setup is a fixed fee, agreed before it starts. [FILL, Tomica: the amount, or the range, and whether it is credited against a first commitment.]

After that, one meter. You pay in credits, a unit like the tokens AI models charge in, for what the AI actually does. There are no platform, maintenance or infrastructure fees on top.

| Plan | Price per credit | Term | Committed credits | Annual minimum |
|---|---|---|---|---|
| On-Demand | $0.002570 | none | none, pay for what you use | none |
| Annual Commit (30% off) | $0.001799 | 12 months | 1,000,000 a month | $21,588 |
| Strategic Commit (50% off) | $0.001285 | 36 months | 1,000,000 a month | $15,420 |

In euros: €0.002185, €0.001530 and €0.001093 per credit; annual minimums €18,360 and €13,116.

What typical activities use, from our deployments (approximate; more complex setups use more):

| Activity | Credits | At On-Demand rate |
|---|---|---|
| A proactive message sent | about 1.5 | under $0.01 |
| A website visit: a guided flow opened, no interaction | about 3.5 | under $0.01 |
| A fully automated guided flow, 9 screens | about 13 | about $0.03 |
| A lead qualification flow, 9 screens with one AI step | about 33 | about $0.08 |
| A lesson solved, 6 questions | about 45 | about $0.12 |
| A conversation with the AI, 4 turns | about 510 | about $1.31 |

- Committed credits arrive monthly, one twelfth of the year. Unused credits expire at the end of each month.
- Use above your commitment is billed at the On-Demand rate.
- Plans stack: add another at any time and its credits add to yours for the overlap.
- Credits are pooled across your projects.
- You get an alert at 80% of your monthly commitment.
- Committed plans include onboarding support for the first 30 days.
- Channel costs, such as SMS and WhatsApp fees, stay with you.

[FILL, Tomica: payment terms; whether prices are shown in both currencies; tax.]

### After the first eight weeks

You see the number against the control group. Then you decide: expand to more people or another use case, change the approach, or stop. [FILL, Bojan and Tomica: what stopping means: notice, data returned or deleted, nothing further owed.]

## When it gets hard

### Who decides what it says

Your team approves how the AI behaves and every playbook before it goes live. Consent and contact limits are enforced by the system, not left to the AI.

### Switching it off

There is a kill switch. [FILL, Juraj: who can pull it (your team, us, or both), how fast it takes effect, and what happens to conversations in progress.]

### It reads the relationship, not just the message

The AI recognises where each relationship stands, and each situation has its own protocol:

- **Someone who prefers to be left alone.** It stops reaching out and stays available when they ask.
- **Someone frustrated, going quiet, or asking how to leave.** [FILL, Mislav: one line on what the protocol does.]
- **Someone leaning on it for what belongs with family, friends or a professional.** It cools things down and draws a boundary.
- **A charged topic.** Politics and social controversies: it stays out of them.
- **Someone in crisis.** Self-harm, abuse, danger: it hands over to a real person.
- **Someone who says stop.** No more messages until they agree again.

## Where we're not a good fit

We'd rather tell you now than in month three.

- **Things people just want done.** Paying a bill, resetting a password, tracking a parcel: a good service flow is enough. We're for decisions people care about getting right: a plan, a loan, a first road bike, a trip.
- **Small customer bases.** Our results come from comparing people who get it with people who don't. Below about [FILL, Mislav: threshold] customers, there aren't enough of either to show a result.
- **Help with a company you're a customer of.** If a company that works with us sent you here, write to them; they run their own assistant.
- **Pressure.** Countdown timers, manufactured urgency, blasting the whole list: we don't build it.
- **Some industries.** Our licence agreements rule out tobacco, distilled spirits, weapons, casinos, gambling and pornography.

## For your review team

One section per reviewer, so each can be forwarded on its own.

### IT and architecture

- **What it connects to.** It reads from the systems you already run (billing, support, usage, CRM) and writes back actions. No data migration; it runs alongside your current tools. [FILL, Juraj: integration list and methods.]
- **Channels.** On your website, by WhatsApp, SMS and email, and in your app. [FILL, Juraj: confirm the list.]
- **On your website.** One line of JavaScript.
- **APIs.** Treated as stable: a breaking change is announced in advance and confirmed with clients before it ships.
- **Hosting.** Microsoft Azure, in the US and the EU. [FILL, Juraj: region choice per client.]
- [FILL, Juraj and Tomica: single sign-on; uptime commitment and support levels.]

### Security

- ISO 27001 certified; working toward SOC 2 Type II. [FILL, Tomica: expected date.]
- Data encrypted at rest (AES-256) and in transit (TLS 1.2 or higher).
- Access on a need-to-know basis, with role-based permissions; every access is logged and monitored.
- Firewalls, intrusion detection and regular security assessments.
- A secure development lifecycle, with OWASP practices built in.
- Incident response follows the NIST process: detect, contain, remove, recover, review.
- [FILL, Tomica: penetration testing (how often, last date); breach notification time; subprocessor list.]

### Data and privacy

- **Your customers' data stays put.** Conversations and personal details stay in your own isolated environment. They are never pooled across companies and are not used to train AI models.
- **Your playbooks stay yours.** The playbooks, rules and results your team builds are your property under our licence agreement. They are never shown to another client, including one in your industry.
- **What we learn is the method.** What improves over time is which approaches help, learned from working with your team on the playbooks and kept only in general form across clients. No names, conversations or customer histories go into it.
- **Our role.** For your customers' data, we act only on your instructions (processor under GDPR). [FILL, Bojan: data processing agreement, link.]
- **Deletion.** End-customer data is deleted within 30 days of a request; some copies may be kept where billing or the law requires. [FILL, Bojan: retention periods.]
- **Control groups.** Comparing people who get the AI with people who don't runs on your customers, under your consent and contact rules.

### Messaging and consent

We build and run assistants for the companies we work with, including over SMS and messaging apps. The same rules apply whether a message comes from us or from a company on our platform.

- **Opt in first.** We only message people who have agreed to be contacted on that channel. No bought lists.
- **Clear sender.** Every conversation says which company it comes from, right at the start.
- **Easy to stop.** To stop receiving messages at any time, write to hello@mindsmiths.com and we'll opt you out.
- **Only what's useful.** Service updates, account and billing information, onboarding, support, and educational content you've opted into. How often you hear from us depends on your account activity.
- **No cost from us.** Message and data rates from your carrier may apply.
- **Your number.** Mobile numbers and consent records are used only to deliver this service. We don't sell personal information, and we don't share opt-in data with third parties for their marketing.

### Legal

- Our Terms of Service and Privacy Policy, each with a plain-English summary: see **Our terms, in plain English** below.
- [FILL, Bojan: our licence agreement, summarised with the same prompt.]
- [FILL, Bojan: data processing agreement.]

### Procurement

- Who you'd contract with: Mindsmiths, Inc., a Delaware corporation (see **Company details**).
- Prices and plans: see **What it costs**.
- [FILL, Tomica: payment terms, insurance, vendor forms (W-9 and others) on request.]

## Our terms, in plain English

Our Terms of Service and Privacy Policy are legal documents, written for lawyers. Below is a plain-English summary of each, written by AI. Here is how we made it, so you or your AI can check it.

### How we made these summaries

On October 11, 2026, we gave an AI (Claude Opus 5.5, made by Anthropic) the full text of each document, as last updated on November 28, 2024, with the prompt below. What follows is its answer, unedited. You can run the same prompt on the full text with your own AI and compare.

The full documents are what count. If a summary and its document disagree, the document wins, and please tell us at [hello@mindsmiths.com](mailto:hello@mindsmiths.com). When a document changes, we run the prompt again.

> I'm about to agree to this document on behalf of my company. Summarize it the way a fair-minded general counsel would brief our CEO before signing: someone who wants a good deal for us, but knows a vendor needs reasonable protections too.
>
> Start with who this document applies to, and what would replace it (for example, a signed contract).
>
> Then cover, in plain English, with the exact numbers, dates and amounts:
> - What we commit to, and what they commit to
> - What it costs, how billing works, and what happens if we pay late or dispute a charge
> - Who owns what: our data, our content, their software
> - What happens to our data and our customers' data: what's collected, why, where it's stored, who sees it, how long it's kept, and how to get it deleted
> - Who is liable for what, and up to how much
> - How either side can change it or end it, and what continues afterwards
> - Which law applies, and how disputes are handled
>
> For each point, say whether it's standard for business software, better for us, or better for them. Don't treat standard protections as red flags, and don't skip anything unusual. Don't add anything the document doesn't say. Leave out points the document doesn't address.
>
> End with the three things our CEO should know before signing, and anything important the document doesn't cover.

### Terms of Service: summary

**Who it applies to.** Anyone using Mindsmiths' website, platform or APIs, including a company whose employee accepts on its behalf. If your company has signed a Platform License Agreement with Mindsmiths, that agreement may replace these terms, except for general use of the website. The terms describe Mindsmiths as a platform as a service for building intelligent agents.

**What we commit to.** Use the services only for legal purposes. Be 18 or older and authorized to bind the company. Keep logins confidential. Take responsibility for everything done under our accounts and by our users, and for the accuracy and legality of the data we put in. Have every consent needed to message our own end users (WhatsApp, SMS, email and others) and follow the law on it. Don't use the services where a failure could cause death, injury or environmental damage. *Standard.*

**What we may not do.** A long list: no copying, reverse engineering or reselling the platform, no probing their security, no spam, no framing their name or logo. Two items go further than usual. Accessing the site or content with "any engine, software, tool, agent" or crawler, other than their own or an ordinary browser, is prohibited, which covers AI assistants. And using the services or content "for any commercial purpose or for the benefit of any third party" is prohibited unless the terms permit it, which sits awkwardly with a license for internal business use. *Mostly standard; those two items are better for them.*

**What they commit to.** A hosted platform with methodology and infrastructure (storage, compute), and a limited, non-exclusive license to build agents for our internal business purposes and to serve our end users through them. An email when they change the terms or services in a way that may significantly affect us, and 30 days' email notice before a price change. No uptime, support level or service credits. *Thin. Common for online terms, light for a business relying on the platform; better for them.*

**What it costs.** Fees follow the payment plan, based on infrastructure, compute and support level, charged as monthly licensing fees. Everything paid is non-refundable. Invoices are due by the date given or service may be terminated. Late payments carry 1.5% a month (or the legal maximum, if lower) plus collection costs. Disputes must be raised within 30 days of the invoice or charge. Service can be terminated for amounts more than 30 days overdue. Continuing to use the service after a price change means accepting it. *Standard.*

**Free trials.** They may offer one. Unless we cancel before it ends, it turns into a paid plan, and we get no notice that the trial ended or that billing started. They can change or end trials at any time without notice. *Better for them, and unusual: many places require notice before a trial converts to paid.*

**Who owns what.** Mindsmiths claims no ownership of our data or content. We give them a worldwide, royalty-free license to use it only as needed to provide the services (and as the Privacy Policy describes). We remain responsible for it and promise we have the rights and consents to use it. Feedback we give becomes theirs to use freely, forever. They keep all rights in the platform. *Standard.*

**Our data.** Covered by the Privacy Policy. They may use and disclose it to provide the services, handle technical problems, investigate security incidents, fraud and spam, protect people from harm, respond to emergencies and comply with the law. We can delete it or ask them to. *Standard.*

**Liability.** The services come "as is", with no promise they will be available, error-free or accurate. They are not liable for indirect or consequential losses, including lost profits and lost data. Their total liability is capped at what we paid in the 12 months before the incident, or €100 if we paid nothing. We indemnify them against claims arising from our use, our content or our breach; they give us no indemnity, including none if their software infringes someone else's rights. *The disclaimer and the 12-month cap are standard. The one-way indemnity, with no protection against IP claims, and a cap that only limits their side are better for them.*

**Changing or ending it.** They can change the terms or the services at any time; significant changes come by email, and continuing to use the service means accepting them. They can change or discontinue any part of the services without notice. We can cancel at any time by email to hello@mindsmiths.com. Fees, feedback, ownership, disclaimers, indemnity, liability limits and dispute terms continue after termination. *One-sided changes are common in online terms and better for them.* We can't assign the terms without their consent; they can assign freely. *Common; better for them.*

**Law and disputes.** Delaware law. A dispute starts with written notice within 30 days, then 30 days of good-faith negotiation (extendable), then mediation in Miami, Florida, with a mediator both sides agree on. If that fails within 60 days, either side can go to court under Delaware law. All of it is confidential. No arbitration and no class-action waiver. *Standard and balanced.*

**The three things our CEO should know before signing**

1. If we sign a Platform License Agreement, that is what governs. These terms are the fallback for the website and anyone without a contract, so negotiate in the agreement, not here.
2. Almost all the risk sits with us: no service level, a one-way indemnity, no protection if their software infringes someone's IP, and a liability cap only on their side. If customer-facing work depends on this platform, get a service level, a mutual cap and an IP indemnity in the signed agreement.
3. They can change these terms by email, and continued use counts as acceptance. In a signed agreement, changes should need both sides.

**What the document doesn't cover:** uptime or support commitments, security measures or breach notification, a data processing agreement, getting our data back when we leave, confidentiality obligations (the survival clause lists "Confidentiality", but there is no such section), and who is responsible for what the AI says to our customers.

### Privacy Policy: summary

**Who it applies to.** Mindsmiths, Inc.'s customers (the policy calls them "Developers"), people who visit the website or contact the company, and the personal data of customers' end users processed on the platform. A separate data processing agreement, if signed, can set different retention terms for end-user data. End users of an agent built on the platform are told to contact the company that runs it, not Mindsmiths.

**Their role.** For our own account data, Mindsmiths decides how it's used (the "controller" under EU law). For our customers' data, it acts only on our instructions (the "processor"). *Standard.*

**What they collect about us.** What we enter in forms, records of our conversations with sales and support, contact and billing details, account names, IP addresses, cookies and web beacons, API keys and access tokens, and information about our company from public sources and data providers (industry, size, website). *Standard.*

**Why.** To deliver the contract; for legitimate interests (understanding customers, managing the relationship, sending marketing, research, accounting and taxes, preventing fraud and security incidents); to meet legal obligations; and for anything we consent to. Website cookies are used to understand visitors and to "tailor and deliver advertisements", and they may use Google Analytics. Marketing emails have an opt-out. *Standard for a software vendor; ad targeting on the website is more than some vendors do.*

**Our customers' data.** It reaches the platform when end users approve access during sign-in, and in the messages sent and received. They use it to provide the service, and for debugging, security investigations, and spam and fraud prevention. Details are left to the product documentation and any data processing agreement. *The processor role is standard; leaving the specifics to other documents is vaguer than usual and better for them.*

**Who sees it.** Service providers bound to protect it; the only subprocessor named is Microsoft Azure (cloud, USA and EU). Authorities, when legally required, and we are told unless the law forbids it; they may challenge requests they think invalid. Their subsidiary, Mindsmiths d.o.o. A buyer, in a sale or merger. They don't share de-identified end-user data except to provide the service, but they may share de-identified or aggregated data about us, the customers, with third parties for research, analytics and "any other legally permissible purposes". *Standard, except the open-ended sharing of aggregated account data, which is better for them.*

**Where it's stored.** It "may be transferred, processed, and stored anywhere in the world", including the EU; they "endeavor" to protect it as the law requires. No transfer safeguard is named. *Better for them. EU buyers usually expect the transfer mechanism to be named.*

**How long, and deletion.** Account data is kept as long as needed for the service, the business and the law. If we close our account, within 30 days they delete our data or de-identify it, keeping what billing, taxes and audits require. End-user data takes up to 30 days to delete; copies may be kept for billing, troubleshooting, fraud prevention and legal holds, and de-identified data may be kept. No fixed retention periods are given. *Standard.*

**Our rights.** Access, correct, delete, restrict, object, port and withdraw consent, by writing to hello@mindsmiths.com, after identity checks. People in the EEA, Switzerland and the UK can complain to a regulator. They don't respond to browser "Do Not Track" signals. *Standard.*

**Security.** They "take steps" to protect data and say the internet can't be guaranteed secure. No specific measures are listed. *Standard wording, thin on substance.*

**Changes.** They can revise the policy at any time and will notify us of material changes as the law requires; continuing to use the services means accepting it. *Standard for privacy policies.*

**The three things our CEO should know before signing**

1. For our customers' data, Mindsmiths acts on our instructions, but this policy leaves what is processed and for how long to other documents. Sign a data processing agreement that spells it out.
2. Data can be stored and moved anywhere in the world. Azure in the US and EU is the only named subprocessor, and no transfer safeguard is named. If we have EU customers, require a region commitment and a named transfer mechanism.
3. Our own account and website data is used for marketing and ad targeting, and aggregated data about us can be shared broadly. Low risk to our customers, but worth knowing.

**What the document doesn't cover:** whether our customers' data is used to train AI models, breach notification timing, specific retention periods, a data protection officer or EU representative, US state privacy rights (such as California's) and opt-out signals like Global Privacy Control, and security certifications.

### Full documents

- [Terms of Service](https://mindsmiths.com/terms-of-service)
- [Privacy Policy](https://mindsmiths.com/privacy-policy)

## About

### Where we are

Mindsmiths, Inc. is a US company, incorporated in Delaware, with people in San Francisco and Miami. We work from home offices, so there's no street address to visit. Our engineering team works in Zagreb, Croatia, at our subsidiary, Mindsmiths d.o.o.

### Who leads what

- **Mislav Malenica,** founder and CEO. San Francisco.
- **Jordan Yates,** VP of Sales. Miami.
- **Tomica [FILL: surname],** COO: pricing, contracts and operations.
- **Juraj Malenica,** Head of Engineering. Zagreb.
- **Martina Silov,** new opportunities and media.

### How it started

In the spring of 2020, Croatia's healthcare hotlines were getting four times more calls than they could handle. Our founder, Mislav Malenica, had spent 20 years as an AI scientist, building medical diagnostic algorithms used on millions of people. So the team set out to build an AI assistant with the Croatian government to take some of the load.

The plan was a diagnostic AI, and it fell apart almost at once. There was no data to train on and no medical guidelines to follow yet. Even the country's best epidemiologists couldn't tell flu from COVID without a test. So the assistant, Andrija, couldn't diagnose anything. What it could do was show up every day: answer what it could, say plainly what it didn't know, and ask how you and your family were doing.

More than 50,000 people used it in the first 15 minutes. Within a week, the load on the call centers had dropped by more than 25%. When the team called people to ask why, they kept hearing the same thing: with Andrija, the situation felt serious but under control.

Soon after, companies in telecom, healthcare, fintech and higher education asked for the same thing for the people they serve.

## Contact

**To see it running on one of your use cases:** write to Jordan Yates, VP of Sales, at [jordan@mindsmiths.com](mailto:jordan@mindsmiths.com), or ask our assistant on this page. The first call takes 30 minutes. Bring the use case you'd start with and the number you'd want it to move. [FILL, Jordan: booking link.]

For anything else, write to the person who handles it, or to [hello@mindsmiths.com](mailto:hello@mindsmiths.com) and we'll pass it on.

- **Pricing, contracts and reselling.** Tomica, COO. [FILL: email.]
- **New opportunities and media.** Martina Silov. [martina@mindsmiths.com](mailto:martina@mindsmiths.com)
- **Technical questions and security reviews.** Juraj Malenica, Head of Engineering. [juraj@mindsmiths.com](mailto:juraj@mindsmiths.com)
- **Your data.** See, correct or delete the data we hold about you. [hello@mindsmiths.com](mailto:hello@mindsmiths.com)

## Join us

Our engineering team is in Zagreb, Croatia. What we build goes live with national telecom operators, fintechs and an airport, in Europe and the US, usually soon after it ships.

The hard part isn't getting a model to write a good message. It's deciding, for one person on one day, whether to send anything at all, and checking later whether that was the right call.

You own a problem and ship it, end to end. If you'd like a detailed plan handed to you each week, it won't suit you. If you'd like to see your work in front of real customers within weeks, it will. Kebab Monday, Squid Friday and karaoke.

### Open positions

- **Software Engineer.** Junior or experienced. Design, build, test and ship with a lot of freedom. We use Python, Java and Vue.js most. Write to [juraj@mindsmiths.com](mailto:juraj@mindsmiths.com).
- **Product.** Work close to customers and shape what gets built: UX, product ownership and project management. Write to [juraj@mindsmiths.com](mailto:juraj@mindsmiths.com).

### Before you write

- Engineering and product roles are on site in Zagreb, at Zavrtnica 17.
- We hire students and full-time employees. Both work full time.
- We don't have machine learning or data science roles.
- There's no form, and you don't need a CV.

## Company details

- **Mindsmiths, Inc.** A Delaware corporation. 1000 N West Street, Suite 1200, Wilmington, DE 19801, U.S.A.
- **Mindsmiths d.o.o.** Our engineering subsidiary. Zavrtnica 17, HR-10000 Zagreb, Croatia. Company reg. no. 081287362, Commercial Court Zagreb. Director: Mislav Malenica.
- **Legal notices.** [hello@mindsmiths.com](mailto:hello@mindsmiths.com)

---

© 2026 Mindsmiths, Inc. · [hello@mindsmiths.com](mailto:hello@mindsmiths.com) · This file is the website.