We built this for our own pipeline before we sold it to anyone.

Every part of Dizenly existed as something we relied on ourselves before it became a feature anyone could buy.

Dizenly is a small engineering team that builds one thing: the system that decides which prospect your team should talk to next, and why. We are not a general automation platform with a prospect module bolted on, and we are not trying to become one.

The product started because our own sales process was a mess. Every quarter began the same way - a spreadsheet of prospects, someone skimming it for anyone who looked promising, and a set of judgement calls that lived in one person's head and nowhere else. Nobody could explain why a name near the top deserved to be there.

So we built the tool we actually needed: something that would take a raw list, score every row against who we were actually trying to reach, rank it, hand each name to the right person, and draft the first message. It was internal for a long time. It didn't have a name that mattered outside the company, and it didn't need one - it just needed to work every morning.

It kept working. Once the internal version was reliable enough that we ran our own pipeline on it, the obvious next question was whether anyone else needed the same thing. Dizenly is that answer - the internal tool, rebuilt as a product, held to the same standard as when we were the only ones using it.

  • 2019

    the year the first scoring prototype was written

  • 1,500

    prospects in the first list we scored end to end

  • 9 mo

    from internal spreadsheet to a working scoring engine

  • 1

    internal tool that turned out to be the actual product

Illustrative figures - Dizenly's founding date and early project history are being finalised for publication.

What we optimise for

Four rules every feature has to survive

These aren't values on a wall. They're the questions we ask before anything ships.

  • The score is explainable

    A 0–100% number with no reasoning behind it is a guess wearing a decimal point. Every score comes with the factor breakdown that produced it.

  • The queue is deterministic

    Same inputs, same ranking, every time. Ties break on a fixed rule, not on whoever refreshed the page last.

  • Honest about LinkedIn's rules

    No unauthorised scraping and no bot logins pretending to be a person. We built around the constraint instead of around it.

  • Remove work, don't add a tool

    The test for every feature is whether it deletes a manual step. If it just adds another dashboard to check, it doesn't ship.

Team

The people behind it

A small team split between the product and the client work that funds it.

  • Founder & CTO

  • Alina Vogel

    Product Lead

  • Ryan Mitchell

    Lead Engineer

  • Emma Clarke

    Design Lead

  • Daniel Oakes

    Delivery Manager

  • Paulina Nowak

    Customer Success Lead

Team names are placeholders pending confirmation. The founder is listed by role only.

Working on Dizenly

We're a small team building a product out of a tool we needed ourselves. If that sounds like your kind of problem, we'd like to hear from you - no open requisitions listed here yet, so tell us what you'd want to work on.

Get in touch

Questions about us

Who builds this, why it works the way it does, and what happens to your data.

Rather ask us directly?

The contact form reaches the people who build the product. We reply within 24 hours on a working day.

Who builds Dizenly?

A small product team in Ahmedabad, Gujarat. The people who scope the product build it and answer the support mail - there is no account layer between you and the engineers.

Why build this around a constraint instead of around the API?

Because there is no general LinkedIn API for outreach, and the tools that behave as if there is are scraping or logging in as you. Both are against LinkedIn’s terms and both get accounts restricted. We built the queue so the software does the judgement and a person does the action.

Is Dizenly live yet?

The platform is in build and the launch date is on the home page. If you want to be in the first group running it on a real list, the contact form is the way in - say what you sell and roughly how big your list is.

How do you handle our data?

Your prospect data stays in your environment and is not pooled, resold or used to train a shared model. The privacy policy and the data processing page set out the detail, and we will sign a DPA.

Start here

Bring one export. Leave with a ranked queue.

Tell us how your team sources and qualifies today, and we will show you the scored, ranked, owner-assigned queue that comes out the other side - and what it replaces.

Not ready to talk? Start the 14-day trial on your own list instead.

  • 14-day free trial
  • No credit card
  • A person replies within 24 hours