Skip to content
Start a project Sign in
Home/About
About Specicon

A machine decides for your customer thousands of times a day. We think it should be able to explain itself.

Specicon is decision infrastructure — a pseudonymous identity layer and a set of engines that pick the right thing for the right person, in 18 milliseconds, with a reason attached. We're building it in the USA and India, for teams everywhere.

Why we built it

A machine that cannot explain itself should not decide.

Specicon exists so the person on the other side of the recommendation can see the reason — and so can the team that shipped it.

Decision traceLive · explained
01ContextSession, device, locale
02BehaviourRecent views and clicks
03ConstraintsStock and budget
04PolicyConsent and guardrails
Recommendation
Why
Matches behaviour
In stock, in budget
Passes policy
Reason attached
Audit logTrace saved
Why we exist

A recommendation is a decision made on someone's behalf.

A group of colleagues
Every person · a decision · a reason attached

Most of those decisions are guesses in good posture — "customers also bought," a rule someone wrote two years ago, a black box no one can question. When they're wrong, the customer pays in wasted time and the business pays in returns.

We started Specicon on a stubborn belief: a decision you can't explain shouldn't ship. So we built an identity layer that reads behavior instead of storing people, engines that reason before they answer, and a reason string that travels with every match — the same words support, merchandising and the customer all see.

Then we made ourselves prove it. Every rollout runs against a live holdout — because trust is earned in evidence, not adjectives.

What we believe

Six principles we actually ship by.

Not wall art. Each of these is a decision we've made about the product, and one you can hold us to.

{{ p.icon }}{{ p.n }}

{{ p.t }}

{{ p.d }}

{{ g.v }}
{{ g.t }}
{{ g.d }}
How we work

Small teams, real ownership, everything written down.

Remote-first, with hubs in the USA and India. We optimize for judgment over process — and we write, because a decision you can't explain shouldn't ship here either.

A small team in a working session
{{ w.icon }}
{{ w.t }}
{{ w.d }}
The people

How the team is organised.

Operators, engineers and scientists who'd rather ship one decision that holds up than ten that mostly work.

{{ m.initials }}
{{ m.role }}

{{ m.bio }}

{{ m.name }}
{{ m.role }}

…and a growing team across three time zones. See who we're hiring →

Careers

Come build the decision layer.

{{ openLabel }}
{{ r.title }}
{{ r.team }}{{ r.loc }}{{ r.type }}
Apply
Don't see your role?

If you can help machines decide well — and explain it — we want to hear from you. Tell us what you'd build.

Send a general application
Why join

The work is hard. The rest shouldn't be.

A team celebrating together
{{ b.icon }}
{{ b.t }}
{{ b.d }}
Join us

Help machines decide well — and explain themselves.

Whether you build the engines or bring them to customers, there's a seat for people who care about decisions that hold up.

The room where it started

A small team building decision infrastructure the slow way — proof first.

Sample imagery · to be replaced with our own
The Specicon team
The teamSmall, and building the slow way.