Skip to content
Vixor

Four modes, one studio.

We are not defined by a medium. Web, email, Telegram, Discord, trading terminals, spreadsheets, phone calls, USSD. The medium is an implementation detail; the work is the thing.

Acquire

Get data that is not handed to you.

Most useful data has no API, or has one that costs more than the data is worth. Acquiring it means going and taking it: logging into a portal, reading a page that changes shape every few weeks, pulling a number out of a PDF. This is the part people quietly do by hand every morning.

On the waitlist: Vixor Monitor.

For example

  • Scraping a supplier portal that has no API
  • Watching prices and stock across a set of listings
  • Pulling figures out of statements and invoices
  • Ingesting a feed nobody publishes cleanly

Execute

Do the repetitive thing, correctly, every time.

The work itself, done the same way on the thousandth run as on the first. Execution is where automation pays for itself twice: once in the time it takes back, and once in the mistakes that stop happening because nobody is doing it tired at 2am.

Shipping: Trade Copier.

On the waitlist: Vixor Pulse.

For example

  • Copying one trade to three hundred accounts
  • Filling and submitting the same form on a schedule
  • Routing and sending email that used to be manual
  • Keeping two systems' records in step

Decide

Delegate judgment, not just motion.

The step past repetition. A system that decides reads a situation and picks, rather than following a fixed script: which of these messages needs a human, which alert matters, whether this signal is still worth acting on. We use a model where it earns its place and deterministic code everywhere else.

Shipping: Signal Copier.

On the waitlist: Vixor Desk.

For example

  • Triaging a support queue and answering what it can
  • Filtering alerts down to the ones worth waking up for
  • Reading a signal and deciding whether it is still valid
  • Classifying and routing incoming work

Reach

Meet work where it actually lives.

Most automation shops are channel shops: they do one platform, and if your work does not happen there, you are not their customer. We treat the medium as a delivery detail. If the work happens on a phone call or a USSD menu, that is where the system goes.

For example

  • Telegram, Discord, Slack, WhatsApp
  • Browser and desktop, including apps with no API
  • Trading terminals on your own machine
  • SMS, USSD and voice

Most builds use all four

The modes are a way to talk about the work, not a menu you pick one item from. Here is what that looks like in practice.

  • Acquire
  • Execute
  • Reach

Broker portal, answered from Telegram

An introducing broker needed client account figures out of a partner portal that has no API and actively resists automated access. Every lookup meant logging in by hand and reading a dashboard.

A browser-automation layer that authenticates against the portal, defeats the bot check, and pulls client balance, equity, credit and trading activity. A Telegram bot sits in front of it: search a client by name, user ID or account number, or list everyone inside a balance range. Sessions are cached for 24 hours and re-authenticate on their own when they expire, and results also sync to Google Sheets.

Lookups went from over 50 seconds to under 3 on a warm session. The portal is now something the team queries from their phone instead of a job somebody sits down to do.

  • Acquire
  • Decide
  • Execute
  • Reach

Topic crawler and reply desk for X

Finding the right conversations on X, early, is a full-time job. So is keeping up with replies once you are in them.

A crawler that spots accounts as they are created and tracks the ones discussing a given topic. It reads mentions and replies, decides which are worth answering, and posts, replies, quotes or reposts where that is the right move. The whole thing is driven from a Discord bot: operators watch what it found and steer it without touching a terminal.

New accounts in a topic surface within minutes of being created, and routine replies go out without anyone opening X.

How a custom build goes

  1. You describe the task

    What you do by hand, how often, and where it happens. If a product already solves it, we say so instead of quoting you for one.

  2. We scope and price it

    A fixed number and a description of what you get, before anything is built. If the scope changes, the number changes and you approve it.

  3. You get the thing

    The system, running, plus the source. It is handed over, not rented back. Where it makes sense it runs on your own hardware.

Tell us what you keep doing by hand

Vixor builds automation that does the work you keep putting off.

Describe your problemSee the products