Book a call

Choose who to talk to

Pick who you’d like to speak with and book a time that works for you.

Dima Blyshchyk, CEO & Founder at Mitrix

Dima Blyshchyk

CEO & Founder

Max Fedaraka, Head of Business Development at Mitrix

Max Fedaraka

Head of Business Development

Industries / Ticketing / Autopricing

Autopricing with a human brake.

Price rules should move faster than a spreadsheet and slower than a mistake. We build an engine that prices by event, section, seat and time to event, inside floors and ceilings you set. Exceptions go to a review queue, and every change lands in an audit trail, so a person can see what moved and why.

Rule-based pricingFloors and ceilingsReview queueAudit trail
Pricing console
RuleActive
PriceWithin bounds
ReviewTwo waiting
PublishPublished
Auditevery change
38%ticket sales lift
2xoperational capacity
Rulespricing logic
Auditevery price change
01 — Capabilities6 connected areas

What we build.

One workflow can touch a referral, a supplier, a delivery team, a patient, a payer and an EMR. We work across the chain, or just the handoff that hurts.

01

Rules by event and seat

A rule can target an event, a section, a seat group or a single seat. Each one carries its own conditions, so a courtside row and an upper deck block follow different logic without separate tooling.

RulesSectionsSeats
02

Time to event

Price behavior changes as the event approaches. You set the curve, and the engine applies it on schedule, so a ticket does not sit at its opening price on the day of the show.

TimingCurvesSchedule
03

Floors and ceilings

Every rule can carry a minimum and a maximum. The engine will not price outside those bounds, which keeps a bad rule or a thin data day from turning into a sale you regret.

BoundsLimitsSafety
04

Exception review

When a price falls outside what the rules expect, it goes to a review queue with the event, the seat and the reason. An operator approves, edits or rejects it. Nothing publishes on its own.

ReviewApprovalQueue
05

Audit trail

Every price change records the rule, the previous value, the new value, the time and the person or process behind it. You can reconstruct why any ticket was priced the way it was.

AuditHistoryTraceability
06

Marketplace alignment

Prices publish to the channels you sell on, within each marketplace's terms. The audit trail covers every channel, so a change made for one listing is visible everywhere it applied.

ChannelsPublishTerms
02 — WorkflowEnd to end

The workflow we cover.

Every step is a handoff. The software has to keep the state, the reason and the evidence together, or operations rebuilds the process in spreadsheets.

01

Set the pricing model

Agree which inputs drive price: event, section, seat, time to event and the demand signals you can access.

Model · Inputs
02

Define floors and ceilings

Set the bounds each event or section must stay inside, so the engine has a hard stop.

Bounds · Policy
03

Write the rules

Turn pricing policy into rules with conditions, schedules and exceptions that operators can read.

Rules · Conditions
04

Build the review queue

Decide which changes need a person, then route those exceptions with the context to approve or reject.

Review · Approval
05

Connect publishing

Publish approved prices to connected marketplaces and keep the audit trail across every channel.

Publish · Audit
06

Tune from results

Watch sales, exceptions and rejected prices, then adjust rules as the pattern becomes clear.

Monitoring · Tuning
03 — Where it breaksFour failure points

Where pricing goes wrong

Manual pricing lags the market, and a rule applied by hand is a rule applied inconsistently. A price left low for a day costs margin, and the hours spent editing numbers cost capacity that should go to events.

01

Prices lag demand

By the time someone updates a price by hand, the event has moved. Sections sell unevenly, and a static price leaves money on the table in one area while it slows sales in another.

02

Rules live in a spreadsheet

Pricing logic sits in a file that one person understands. When they take a day off, the logic stops. When they leave, it leaves with them.

03

No record of changes

A price changes and nobody can say who changed it or why. Disputes take longer, and a bad rule can run for weeks before anyone connects it to weak sales.

04

Underpriced inventory

Tickets sell fast at the wrong price, and speed hides the mistake. The seats are gone, the revenue is gone, and the pattern only shows up in a report after the event.

04 — ModulesShipped or scoped per workflow

What the build is made of.

Modules follow the workflow, not a product catalogue. Each one gets an owner, an integration boundary and a way to reconcile with the system of record.

01Rule builder

A place to write conditions for events, sections, seats and time to event.

02Demand inputs

The signals you allow the engine to read, connected and refreshed on a schedule.

03Bounds guard

Floors and ceilings enforced before any price reaches a marketplace.

04Review queue

Exceptions that need a person, with context to approve, edit or reject.

05Audit log

Each change recorded with the rule, the old value, the new value, the time and the actor.

06Publish gateway

Approved prices pushed to connected marketplaces within each channel's terms.

05 — EvidencePublic proof

What it produced.

Representative ticketing work. Client names are under NDA; the workflows and numbers are what we can share.

Case study

Online ticketing platform

The public case reports a 38% lift in ticket sales and 2x operational capacity after distribution and pricing moved onto one platform. Underpriced sales were minimized as rules replaced manual edits.

Read the case
Capability

Marketplace distribution

Pricing only matters if it reaches every channel. Our distribution layer lists, updates and delists across marketplaces from the same record the pricing engine writes to, so a new price lands where the tickets live.

See distribution
Industry

Ticketing

Distribution, pricing, order settlement and venue access share one inventory model. Pricing rules take effect across the same tickets the rest of the platform tracks, which keeps a price change and its listing from drifting apart.

Explore ticketing
06 — ApproachBuild, buy or extend

Build or buy an autopricing engine

Buy a rule editor if that is all you need. Most teams also need the inventory model, marketplace publishing and the audit trail that finance asks for, and those sit under any pricing tool. We build the engine on the same platform that runs distribution.

01

Buy when you sell on one channel with simple pricing and no audit requirement.

02

Build when pricing rules live in a spreadsheet that one person maintains.

03

Build when finance needs a record of every price change and who approved it.

04

Either way, keep the rule logic and the audit data yours and exportable.

07 — StackChosen per constraint

What we build it with.

Existing platforms respected, new surfaces kept boring. The stack follows the integration and compliance constraints.

TypeScriptNode.jsPythonPostgreSQLRedisKafkaReactGraphQLDockerAWS
Platforms and systems
WebiOSAndroidOperator dashboardAdmin consoleREST APIsWebhooksTablet
08 — FAQShort answers

Questions buyers ask.

If yours is not here, send it. We answer in plain language, with the constraints we would check first.

How do the pricing rules work?

Rules set conditions on event, section, seat and time to event, and each rule produces a price inside the floors and ceilings attached to that inventory. Rules run on a schedule and on inventory changes, so a new listing gets a price without a manual edit.

How do floors and ceilings work?

Every rule can carry a minimum and a maximum. The engine will not publish outside those bounds, even if a rule's condition suggests a higher or lower number. Bounds can differ by event, section or seat, and any change to them is recorded in the audit trail.

What demand data does the engine use?

The signals you can legitimately access: your own sales, listing views, search interest and comparable events. We agree the inputs before the rules are written, and we do not assume access to data a marketplace does not provide.

How much human control is there?

Rules run on their own, and exceptions stop at the review queue, where an operator approves, edits or rejects each one before it publishes. You decide what counts as an exception, and you can widen or narrow that as the team builds confidence.

Does it publish to marketplaces?

Yes, through the same distribution layer we use for listing and delisting. Prices reach connected channels within each marketplace's terms, and the audit trail covers the change wherever it applied. A channel that cannot accept a price update shows up as an exception.

How long does a build take?

It depends on how many rules you need and whether demand inputs are already available. A first version with floors, ceilings and a review queue can run before every rule is written. We scope the rest once the model is in place.

Bring us the workflow that hurts.

Tell us where the handoff breaks: listing, pricing, fulfilment, settlement or venue access.