We build digital products that work in the real world.

Identity checks, document handling, lead scoring, customer chat — built as deterministic workflows with a written data boundary, and shipped in days.

Tallinn-based. EU-focused. We still do what we always did: small digital products, discovered, built, and launched — clear enough to run yourself.

Work that fits inside your product.

Most EU teams that need an AI feature don’t need an ML team. They need one integration built correctly, with the data path written down before anything ships.

No ML team, and no reason to hire one

Hiring an ML engineer to ship a single verification flow is the wrong shape of cost. The work is integration work: pick the provider, constrain it, wire it into the product you already have, and make the failure cases boring.

Compliance decided first, not retrofitted

Processor agreements, EU data residency, and terms that exclude training on your inputs get settled before the first line of code — alongside professional secrecy duties where they apply. You keep the document that says what goes where.

A small build, not an integration programme

The enterprise alternative is a six-figure quote on a quarterly cadence. Most teams need one workflow, working, this month — priced as a build rather than a retainer, and handed over so you’re not renting it back from us.

Who this is for

  • Fintech and payments

    10–100 people · post-seed to Series A · PSD2 and KYC scope

    Identity verification and AML screening embedded inside their own product, instead of the checks being rebuilt from scratch.

  • E-commerce and SaaS

    5–50 people · fraud pressure and a rising support load

    Fraud prevention and a customer-facing chatbot at plug-in level, with an API path left open for the logic that turns out to be specific to you.

  • Professional services

    Law, accountancy, consulting · bound by professional secrecy

    Client-facing workflows with deterministic outcomes and an audit trail that a regulator, or a partner, can follow after the fact.

  • Marketplaces

    10–200 people · vendors onboarding continuously

    KYC and KYB across several providers behind one interface, one bill, and the ability to switch provider without rewriting the onboarding flow.

What we can point at

Email Verifier — our own integration

A Chloe & Matt reference case. We built a GDPR-first email verifier that checks syntax, domain, MX records, the SMTP handshake, catch-all status, and role-address patterns, then bills only for decisive verdicts — valid, invalid, disposable. Catch-all and unknown results are free, and the false-positive rate is published and dated. Same shape of work, same data discipline, just pointed at ourselves first.

See how it’s built →

Pistiik OÜ — helping an Estonian verification broker scale identity checks

We built the AI integration behind Pistiik’s identity-verification chatbot. Pistiik is an Estonian KYC/KYB/AML broker that needed a single interface to route each verification request to the right provider. We wired an AI routing layer into their chatbot and email flows so that a user’s check is sent to the provider that matches their geography and document type — KYC from €2.99, KYB from €14.99, pay-per-use with no annual subscription.

The result: Pistiik can offer instant verification to startups and fintechs without maintaining provider integrations in-house, and their team can switch or add providers without rewriting the customer-facing flow.

pistiik.com ↗

Tell us the workflow, the data it touches, and the deadline. We’ll say whether it’s a two-week integration, a bigger job than you think, or a bad idea.

Describe the integration

What we build

Around the integration work, we still run the whole small-product loop: discover, build, market, sell. Each one starts from a real problem and stays small enough to explain in a sentence.

Product discovery

consulting & memos

A short discovery engagement: who has the problem, who will pay, what already exists, and whether the idea is worth building. You get a decision memo, not a roadmap.

Good fit: founders, CEOs, and operators with a use case but no certainty whether it is worth shipping.

Focused digital products

small, clear builds

If discovery says yes, we build a bounded product — not a platform, not a miniature startup inside your company. Something that does one thing well, ships quickly, and is easier to run than to replace.

Good fit: small capabilities where simpler is better.

Growth assets

content & launch support

A product only matters if people ready to use it can find it. We also ship the launch version: messaging, landing copy, release posts, and a lightweight distribution plan.

Good fit: teams that want to stay tight and still do the launch half well.

  • Rhythm check — a 30-day preview of whether the product actually fits
  • Developer handoff — working code plus notes a person can change later
  • Launch copy — message, page, and release notes in one pass
  • Light support — a window of direct support while adoption settles
  • No expansion without review — changes stay small unless both sides agree

This is what a small product engagement looks like

We do not start with a full build. Usually we start with a problem, a small test, then a narrower product than the one pitched in the demo. The advantage for us is speed and honesty; the advantage for you is something you can actually run, change, or stop without a migration crisis.

The longer a product lives, the more we care about the boring parts: clarity of interface, quality of default behavior, and how simple the unexpected case looks when it appears at eleven in the evening.

Where we’d be careful

If the demo is doing work the finished product will not do, we say so. Good software still needs intent to use it. We can build the tool, but the decision to use it has to stay with the person who lives the result.

How we work

No account managers. No bench of juniors learning on your project.

Talk to us directly

Message us like a teammate. Replies usually come in hours, not days.

See the work as it happens

We show you what we built and explain the decisions behind it, in plain language.

Straightforward payment

Half up front, half on delivery. For smaller jobs we’ll find something that suits.

Short timelines

Most integrations ship in days. You’ll see something working early.

You own all of it

Code, documentation, deployment notes. If we part ways, you’re not stranded.

We’ll tell you the truth

If something will blow your budget, we say so. If there’s a simpler way, we suggest it. If you don’t need us, we say that too.

Asep Bagja Priandana

The people who own the decision

Chloe & Matt OÜ is a small software company in Tallinn, Estonia. Asep Bagja is our board member, who signs off on major decisions, provides direction, and sets the tone. He does not build, but he owns the outcome.

We are a two-person studio. Chloe handles strategy and growth; Matt handles engineering. We are Estonian. We are listed in the Estonian business registry (reg. 14305217). GDPR compliance is structural, not contractual.

We build with AI assistance — we use AI tools to write and review code faster, and we are transparent about that when it matters to a project. But you are working with people. A real person will answer your email, make your calls, and sign your contract.

Questions people actually ask

Are you a real company I can hire?

Chloe & Matt OÜ is a registered Estonian company (reg. 14305217). Asep Bagja is our board member. We sign real contracts, invoice through the Estonian system, and you deal with the same people from day one. That is the whole relationship, and it is why we keep builds small.

What does “AI-native” mean for our work together?

It means we use AI to write and ship code faster, and we are up front about that. It does not change how we work: you get a real person on every call, written data boundaries in every integration, and code you can run yourself. We built one AI integration on our own first — the email verifier — so you can see how we handle data, compliance, and failure cases before we touch yours.

How is this different from an agency?

We are smaller by design. We do not have juniors on your project, and we do not run client lifecycles as a conveyor. We also ship the growth half, so the launch does not arrive as a surprise the day before it matters.

What does “small product” mean here?

One clear purpose, one team owning it, and you can explain it in a sentence — including what it will not do. If you need a platform, we will say so.

What do I own at the end?

Code, copy, documentation, and deployment notes are yours. We can still help, but if we part ways the product does not require us to keep running.

What happens after launch?

A short support window while adoption settles. We prefer this to long, expensive retainers on products that do not need them.

Do you take every project?

No. If the demo is doing work the product will not, we will tell you. If the simpler version makes more sense, we will suggest that. An honest “no” is a useful deliverable.

Tell us what’s not working

Describe the thing that’s eating your team’s week. We’ll tell you honestly whether we can help, roughly what it would cost, and whether it’s worth doing at all.