SettleOps

CEO / Founder

Launch new money scenarios faster. Whether or not you already have your own payment layer

Bring new capabilities to market fasterUse a ready operations layer instead of building one.

SettleOps is an SDK for the scenario in your code, a control panel for money movement, recovery after failures and ready connections to rails.

Enter your own numbers

An engineer costs ₽ gross per month.

With SettleOps: engineer for 1 week.

On your own payment layer: engineer for – months.

From scratch: engineer for – months.

Salary costs before launch: with SettleOps, 1 week, ₽75,000; on your own payment layer, 1–2 months, ₽300,000 – ₽600,000; from scratch, 6–12 months, ₽1,800,000 – ₽3,600,000.

The estimate covers salary costs only. Infrastructure, taxes and employer contributions, management, operations and support are not included.

One person-week to integrate with SettleOps allows for business logic changes on your product’s side; it is not a guaranteed launch date.

First-year cost

Volume: operations per month.

SettleOps tariff — ₽12 per operation of any type.

Payments, refunds and payouts are charged separately.
The fee depends on the payment method and the payment system.
More about pricing.

Engineer load per month for code maintenance:
with SettleOps , on your own payment layer , from scratch .

What does maintenance include?

This is the work of your engineers on your product’s side.

With SettleOps: supporting the integration, updating the SDK/API, diagnosing issues on the client side.

On your own payment layer: maintaining the new scenario, fixing bugs, handling failures, updating integrations and tests.

From scratch: maintaining the whole operational layer, including scenarios, payment system integrations, fault tolerance and monitoring.

The estimate covers salary costs of engineering maintenance after launch within the first 12 months. It excludes infrastructure, taxes and employer contributions, and fees for money actions.

Suppose the revenue from your product is ₽ per month.

SettleOps launchSettleOps tariffbuilding your own solutionduration rangemaintenancethe product earns

The comparison covers development, maintenance and use of the operational layer.
Fees for payments, refunds and payouts are not included.

First-year cost: with SettleOps ₽1,837,500; on your own payment layer ₽1,950,000 – ₽2,100,000; from scratch ₽3,600,000. Revenue over 12 months: with SettleOps ₽3,525,000; on your own payment layer ₽3,000,000; from scratch ₽0.

What this means for your business

Example for 10,000 operations per month

Cost per operation with SettleOps

₽15.64

Cost on your own layer

₽19.5–21

Cost from scratch

no operations

within the first 12 months this path does not launch

With these parameters, SettleOpsreduces the estimated cost of the operational layerby ₽112,500 – ₽262,500 compared with your own layerand by ₽1,762,500 compared with building from scratch over 12 months.

Cut development and maintenance costsYour team focuses on product business logic, SettleOps handles the routine.

Your team can maintain only the product business logic code.
Delegate everything else to the operational layer.

Put in your own numbers

An engineer costs ₽ gross per month.

Engineers per month on code maintenance:
with SettleOps , on your own payment layer .

What does maintenance include?

This is the work of your engineers on your product’s side.

With SettleOps: supporting the integration, updating the SDK/API, diagnosing issues on the client side.

On your own payment layer: maintaining the whole operational layer, including scenarios, payment system integrations, fault tolerance and monitoring.

The estimate excludes infrastructure, taxes and employer contributions.

Volume: operations per month.

SettleOps tariff — 12 ₽ per operation of any type.

Payments, refunds and payouts are charged separately.
The fee depends on the payment method and payment system.
More about pricing.

Maintenance costs: with SettleOps ₽150,000 per month, ₽1,800,000 over 12 months — maintenance ₽30,000 and tariff ₽120,000; on your own payment layer ₽300,000 per month, ₽3,600,000 over 12 months.

Maintenance costs

code maintenanceSettleOps tariffsaving

With these numbers, SettleOpscuts the cost of maintaining the payment layerby ₽150,000 per month — ₽1,800,000 over 12 months.

The comparison covers engineer costs for code maintenance and the SettleOps tariff.
Fees for payments, refunds and payouts are not included.

Run hundreds of money actions as one managed operationHand SettleOps a batch of payments, refunds or payouts.
It executes the actions, retries failures by the rules and shows the result of the whole operation — no manual check of every step.
You createSettleOps executes
EventPeriod closed, November 30
Operation200 payouts to sellers
one SettleOps operation
Failedretried, then sent for review

Work out what batch payments and payouts will cost in the first year.
Enter your own figures.

Batches: a week, each one a single SettleOps operation.

That is ≈ 65 SettleOps operations a month.

Manual work

Technical preparation and manual submission of one batch takes h.

Checking the result of one operation takes min, successful and failed actions alike.

With your own code or with SettleOps, exceptional cases still need manual review: suppose % of batches hit one, and each takes min.

An employee costs ₽ a month.

Development and maintenance

An engineer costs ₽ gross a month.

Your own code: mo of development, engineers maintaining the code.

What does your own code include?

This is code your team writes and maintains itself.

Splitting a batch into money actions and building the register for the bank.

Each action exactly once: none skipped when a server fails and no double payout.

Retrying failed actions and sending those that still fail for review.

Partial execution: the batch result when some of its actions have failed.

Reconciling batch results with the bank.

Tracking each action through to its final status.

With SettleOps: wk of integration, engineers maintaining the code.

What does maintenance include?

This is the work of your engineers on your product’s side.

With SettleOps: supporting the integration, updating the SDK/API, diagnosing issues on the client side.

SettleOps fee — ₽12 per operation of any type.

Payments, refunds and payouts are charged separately.
The fee depends on the payment method and payment system.
More about pricing.

First year: your own code ₽2,228,646, manual batches ₽731,250, SettleOps ₽459,855. The manual process is cheaper below 9.2 batches a week.

When does SettleOps pay off?

First year at 15 batches a week

Calculation details

Your own code — ₽2,228,646

development: 2 mo × ₽300,000 = ₽600,000

code maintenance: 0.5 engineers × ₽300,000 × 10 mo = ₽1,500,000

manual work: batches by hand while development lasts, then reviewing exceptional cases = ₽128,646

With SettleOps — ₽459,855

integration: 1 wk = ₽75,000

code maintenance: 0.1 engineers × ₽300,000 × 11¾ mo = ₽352,500

manual work: batches by hand while integration lasts, then reviewing exceptional cases = ₽23,190

fee: ₽12 per operation × ≈ 764 operations a year = ₽9,165

manual workdevelopment and integrationcode maintenanceSettleOps feeSettleOps levelmore than with SettleOps

Calculation details

Manual batches — ₽731,250

manual work: 1.5 h × ₽625 × 52 batches = ₽48,750 for each weekly batch, × 15 = ₽731,250

With SettleOps — ₽459,855

integration: 1 wk = ₽75,000

code maintenance: 0.1 engineers × ₽300,000 × 11¾ mo = ₽352,500

manual work: batches by hand while integration lasts, then reviewing exceptional cases = ₽23,190

fee: ₽12 per operation × ≈ 764 operations a year = ₽9,165

Threshold — 9.2 batches a week

at 15 batches a week — above the threshold: SettleOps is cheaper than manual batches by 731,250 − 459,855 = ₽271,395

SettleOps is cheaper than the manual process from about 9 batches a week.Exact threshold for the current figures: 9.2 batches a week.

Every batch handled by hand adds to the yearly spend. Spend on SettleOps grows much more slowly — most of it goes on integration and maintenance.

Batches a week15 batches a week

threshold 9.2

SettleOps saves ₽1,768,791 over in-house development in the first year.At 15 batches a week, SettleOps saves ₽271,395 over the manual process.

Calculation assumptions

One batch is one SettleOps operation, and the fee is ₽12 per operation however many money actions it holds. A month has 52 ÷ 12 weeks.

By hand, a batch is technically prepared, submitted, and its operation result checked as a whole. Your own code and SettleOps take over preparation, submission and checking; only manual review of exceptional cases remains.

Your own code: development while batches are handled by hand, then maintenance and reviewing exceptional cases.

Freed-up time does not necessarily mean a direct cut in spend. The estimate excludes infrastructure, taxes and employer contributions, and fees for payments and payouts.

Split the money once a deal is doneTake the payment right away and split the money once the deal goes through.
Your product makes the call on the deal. SettleOps carries out the money actions it needs and sees them through to the end.
You createSettleOps executes

Operation ₽12

DealOrder #10482
on a marketplace, ₽18,400
Operationone SettleOps operation
payment, decision, split
Decisionfrom your system
6 h timeout

Work out what splitting the money on deals will cost in the first year.
Enter your own figures.

Deals: a week, each one a single SettleOps operation.

That is ≈ 433 SettleOps operations a month.

Manual work

Tracking the decision by hand and starting the money actions takes min per deal.

Checking the result of one operation takes min, successful and failed actions alike.

With your own code or with SettleOps, exceptional cases still need manual review: suppose % of deals hit one, and each takes min.

An employee costs ₽ a month.

Development and maintenance

An engineer costs ₽ gross a month.

Your own code: mo of development, engineers maintaining the code.

What does your own code include?

This is code your team writes and maintains itself.

Accepting the payment and holding the money until the deal is decided.

Waiting for the decision with a timeout and a default action when none arrives.

The split: payouts to several parties in a set order.

Refunding the buyer on cancellation and reversing payouts already made.

Each payout exactly once: none skipped when a server fails and no double payout.

Tracking each deal through to its final status.

With SettleOps: wk of integration, engineers maintaining the code.

What does maintenance include?

This is the work of your engineers on your product’s side.

With SettleOps: supporting the integration, updating the SDK/API, diagnosing issues on the client side.

SettleOps fee — ₽12 per operation of any type.

For operations with an external decision, the first decision is included in the price; each additional one costs ₽12.
Payments, refunds and payouts are charged separately.
The fee depends on the payment method and payment system.
More about pricing.

First year: your own code ₽2,493,750, manual splitting ₽812,500, SettleOps ₽558,565. Manual splitting is cheaper below 62.8 deals a week.

When does SettleOps pay off?

First year at 100 deals a week

Calculation details

Your own code — ₽2,493,750

development: 3 mo × ₽300,000 = ₽900,000

code maintenance: 0.5 engineers × ₽300,000 × 9 mo = ₽1,350,000

manual work: deals by hand while development lasts, then reviewing exceptional cases = ₽243,750

With SettleOps — ₽558,565

integration: 1 wk = ₽75,000

code maintenance: 0.1 engineers × ₽300,000 × 11¾ mo = ₽352,500

manual work: deals by hand while integration lasts ₽16,927 + reviewing exceptional cases ₽53,038 = ₽69,965

fee: ₽12 per operation (first decision included) × ≈ 5,092 deals over 11¾ mo after integration = ₽61,100

manual workdevelopment and integrationcode maintenanceSettleOps feeSettleOps levelmore than with SettleOps

Calculation details

Manual splitting — ₽812,500

manual work: 0.25 h × ₽625 × 52 deals = ₽8,125 for each weekly deal, × 100 = ₽812,500

With SettleOps — ₽558,565

integration: 1 wk = ₽75,000

code maintenance: 0.1 engineers × ₽300,000 × 11¾ mo = ₽352,500

manual work: deals by hand while integration lasts ₽16,927 + reviewing exceptional cases ₽53,038 = ₽69,965

fee: ₽12 per operation (first decision included) × ≈ 5,092 deals over 11¾ mo after integration = ₽61,100

Threshold — 62.8 deals a week

at 100 deals a week — above the threshold: SettleOps is cheaper than manual splitting by 812,500 − 558,565 = ₽253,935

SettleOps is cheaper than manual splitting from about 63 deals a week.Exact threshold for the current figures: 62.8 deals a week.

Every deal handled by hand adds to the yearly spend. Spend on SettleOps grows much more slowly — most of it goes on integration and maintenance.

Deals a week100 deals a week

threshold 62.8

SettleOps saves ₽1,935,185 over in-house development in the first year.At 100 deals a week, SettleOps saves ₽253,935 over manual splitting.

Calculation assumptions

One deal is one SettleOps operation with one decision: the fee is ₽12 per operation with the first decision included, however many payouts the operation holds; the estimate has no additional decisions. A month has 52 ÷ 12 weeks.

Your system makes the call on the deal on every path, and the time spent on the business decision itself is not counted. Your own code and SettleOps take over starting payouts or refunds by hand and checking the result: the outcome arrives as a status and a webhook; only manual review of exceptional cases remains.

Your own code: development while deals are handled by hand, then maintenance and reviewing exceptional cases.

Freed-up time does not necessarily mean a direct cut in spend. The estimate excludes infrastructure, taxes and employer contributions, and fees for payments and payouts.

Run money operations on a scheduleSet the schedule once, and SettleOps runs the operations on time.
No scheduler of your own to build and no manual runs.
You setSettleOps runs
StartNovember 1, 10:00
Repeatevery month on the 1st at 10:00
Runs3including the first

Work out what scheduled runs will cost in the first year.
Enter your own figures.

Scheduled runs: a week, payments and payouts.

That is ≈ 17 SettleOps operations a month.

Manual work

Today each run is prepared and started by hand: h per run.

Checking the result of one run takes min, successful and failed alike.

With your own code or with SettleOps, exceptional cases still need manual review: suppose % of runs hit one, and each takes min.

An employee costs ₽ a month.

Development and maintenance

An engineer costs ₽ gross a month.

Your own scheduler: mo of development, engineers maintaining the code.

What does your own scheduler include?

This is code your team writes and maintains itself.

Storing schedules and working out the next run: the calendar, time zones, the 31st in a short month.

Running exactly once: no skipped run when a server fails and no double payment.

Counting runs and stopping after the last one.

Changing and cancelling a schedule.

Tracking each run through to its final status.

With SettleOps: wk of integration, engineers maintaining the code.

What does maintenance include?

This is the work of your engineers on your product’s side.

With SettleOps: supporting the integration, updating the SDK/API, diagnosing issues on the client side.

SettleOps fee — ₽12 per operation of any type.

Payments, refunds and payouts are charged separately.
The fee depends on the payment method and payment system.
More about pricing.

First year: your own scheduler ₽2,199,306, manual runs ₽585,000, SettleOps ₽444,253. SettleOps pays off above 3.1 runs a week.

When does SettleOps pay off?

Estimate for 4 runs a week over a year

Calculation details

Your own scheduler — ₽2,199,306

development: 2 mo × ₽300,000 = ₽600,000

code maintenance: 0.5 engineers × ₽300,000 × 10 mo = ₽1,500,000

manual work: runs by hand while development lasts, reviewing exceptional cases = ₽99,306

With SettleOps — ₽444,253

integration: 1 wk = ₽75,000

code maintenance: 0.1 engineers × ₽300,000 × 11¾ mo = ₽352,500

manual work: runs by hand while integration lasts, reviewing exceptional cases = ₽14,309

fee: ₽12 per run × ≈ 204 runs a year = ₽2,444

manual workdevelopment and integrationcode maintenanceSettleOps levelmore than with SettleOps

Calculation details

Manual runs — ₽585,000

manual work: 4.5 h × ₽625 × 52 runs = ₽146,250 for each weekly run, × 4 = ₽585,000

With SettleOps — ₽444,253

integration: 1 wk = ₽75,000

code maintenance: 0.1 engineers × ₽300,000 × 11¾ mo = ₽352,500

manual work: runs by hand while integration lasts, reviewing exceptional cases = ₽14,309

fee: ₽12 per run × ≈ 204 runs a year = ₽2,444

Threshold — 3.1 runs a week

at 4 runs a week — above the threshold: SettleOps is cheaper than manual runs by 585,000 − 444,253 = ₽140,747

Every extra manual run adds to the yearly spend. Spend on SettleOps grows much more slowly — most of it goes on integration and maintenance.

Runs a week4 runs a week

threshold 3.1

SettleOps saves ₽1,755,053 over your own scheduler in the first year.At 4 runs a week, SettleOps saves ₽140,747 over manual runs.

Calculation assumptions

Your own scheduler: development while runs are done by hand, then maintenance and reviewing exceptional cases.

Freed-up time does not necessarily mean a direct cut in spend. The estimate excludes infrastructure, taxes and employer contributions, and fees for payments and payouts.

Questions and answers

What is an operation? Is it a payment or a payout?

An operation is a container for financial actions: payments, refunds and payouts. It usually maps to a business transaction in your product. For example, an apartment rental deal consists of the tenant’s payment and the payout to the owner.

Is this some kind of payment gateway?

No. SettleOps is a payment operations layer that sits between your product and payment gateways. It runs the whole operation and routes payments, refunds and payouts through rails that are already connected, providing orchestration, oversight and resilience.

Why not write this ourselves — with AI in a week?

A happy-path scenario is quick to write. Everything else is expensive: retries and rail failover, timeouts, partial execution, disputed outcomes, audit. That is SettleOps.

We already have a payment layer. Why do we need SettleOps?

Launch new money scenarios without expanding your own infrastructure for running them. If SettleOps already supports the scenario you need, you only have to integrate it into your product. You won’t have to build and maintain new mechanisms for orchestration, retries, timeouts and execution control yourself.

Won’t we become dependent on you?

Your code works with operations through the API and webhooks, not with provider models.

What if we decide to stop using SettleOps?

Your business processes stay in your product. You can stop creating new operations in SettleOps and move their execution to your own system or another provider. Operation history is available through the provided export mechanisms; operations created earlier must be completed or settled before you disconnect.

What happens if SettleOps itself goes down?

An accepted operation is stored together with its plan and attempts and continues after recovery. Nothing is restored from memory.

How much does it cost?

Pricing is not fixed yet — we’ll discuss it on the pilot.

Discuss a pilot