~6 min read · Effective 1 June 2026

Priced by formula. Not by quote.

price = $160 × hours^0.7

Same inputs, same price. Every time.

→$2,11540 productive hours · Remote tier (×1.0) · before USDT −15% · effective rate $53/h, down from $160 the first hour

I bill productive hours only — the time the work actually takes, nothing padded.

A 5-day RouterOS build — 40 productive hours — runs $2,115 at Remote tier. Every price here is a point on the same curve.

Sessions

Duration	Rate	$/h
≤30 min	free	—
1 hour	$160	$160
2 hours	$260	$130
4 hours	$420	$105
8 hours	$685	$86

Projects

Duration	Rate	$/h
2 days	$1,115	$70
3 days	$1,480	$62
5 days	$2,115	$53
10 days	$3,440	$43
14 days	$4,350	$39

Prices are rounded to $5.

Why this formula

The exponent α = 0.7 makes the curve sublinear — the first hour carries the full context load, and every hour after it costs less. Concentrated work amortizes that load, so the effective rate falls as the engagement deepens. The curve is the whole pricing policy. No tiers of discount, no negotiation. Formula, not mood.

At 1 hour you pay $160. At 40 hours the effective rate drops to ~$53/h — the same curve, evaluated at volume. The first hour is the expensive one because it buys the context the rest of the engagement runs on: your topology, current state, constraints. Nothing after it is re-learned.

First hour absorbs the full context load — your topology, current state, constraints. Longer engagements amortize the context load across more hours. The effective rate decays from $160/h to ~$53/h at 40 hours.

Track record

7 of 10 MikroTik certs · 94% avg

Founded MikroTik Academy Vietnam · 11K+ members

~10 years · zero breaches since 2015

5 MUM talks · listed on mikrotik.com

Certifications and consultant listing verifiable on mikrotik.com.

The depth behind every engagement, mapped domain by domain. Explore the expertise map →

You’re buying depth that compounds — the deeper the work goes, the less each hour costs.

Rate decay

Effective rate decays with engagement length. 1h → 112h (max billing cycle).

Calculator

Drag the slider. See your price.

Hours: 8

1h40h

Tier

Pay in USDT (−15%)

Total

$685

Effective rate

$86/h

Warranty

1 year

Billing cycle

14 days

Service tiers

Each tier multiplies the base rate.

Most engagements run at Remote. Live, Advisory, and Emergency exist for when the work demands them.

Remote

×1.0

I solve it, you get results.

Scheduled config, maintenance, batch updates

Live

×1.5

We solve it together, in real time.

Screen sharing, debugging, training-adjacent

Advisory

×1.75

I teach, you learn, we validate.

AI workflows, cert prep, architecture review

Emergency

×2.0

Everything stops. Any hour. Immediate.

Production down, security breach, off-hours

Which tier?

Am I working alone? → Remote

Are you watching / screen-sharing? → Live

Am I teaching you something? → Advisory

Is it 2 AM and production is down? → Emergency

Tier	8h Price	Eff. Rate
Remote	$685	$86/h
Live	$1,030	$129/h
Advisory	$1,200	$150/h
Emergency	$1,370	$171/h

Full tier definitions and drift rules →

Managed MikroTik

For a network already in production — a standing line to the same engineer, priority response, and your context kept loaded between months. The formula on a monthly cadence, not a discount.

$420/mo — 4 productive hours at Remote rate included. USDT −15% → $355/mo. Invoiced after the month, never in advance.

·4 productive hours each month at Remote rate — config reviews, firmware-upgrade planning, change-window support.
·Priority response — your requests jump ahead of the project booking queue, during working hours.
·Persistent context — your topology, addressing plan, and current state stay loaded between months, so retained work skips the first-hour context reload.
·Overflow and any Live, Advisory, or Emergency work bill at the standard formula; the $420 monthly credit applies first.

Month-to-month, cancel anytime with 30 days’ notice. Invoiced after each month — never in advance; USDT −15% → $355/mo. Unused hours do not roll over. Overflow bills at the standard formula on the month’s total productive hours, the $420 credit applied first — retained work is never re-charged a first hour. Live, Advisory, and Emergency work bill at their multipliers.

The $420 is the formula’s 4-hour price. What it buys between tickets is priority and a context I never reload — the first-hour context load I would otherwise bill on every fresh engagement.

Start a retainer →

100% post-delivery payment on verified results

No deposits. No milestones. I carry the risk.

Warranty

Scales with engagement. More hours = longer warranty. Capped at 36 months.

Engagement	Warranty
1 hour	6 weeks
4 hours	6 months
8 hours	1 year
16+ hours	2 years
24+ hours	3 years

1 hour = 6 weeks. 24+ hours = 3 years. Warranty covers post-delivery support for the work performed.

Not a fit if

MikroTik and RouterOS only, no general IT. The formula is deterministic, so there is no opening offer to negotiate down. “I want it done faster” is not an Emergency. A five-minute favor falls under the free tier.

Common questions

Why does spread work cost more?

Each idle gap that exceeds the earned context window closes the billing cycle. A new cycle means a new first hour — and the first hour absorbs the full context reload: your topology, current state, constraints. A sprint amortizes that cost across more hours.

Can I negotiate the price?

No. The formula is deterministic — same inputs always produce the same price. This protects both sides: you know exactly what you'll pay before we start, and I don't have to guess what the market will bear. The only discount is −15% for USDT payment.

What counts as a billable hour?

Productive hours only, at 0.5h granularity. Waiting for your response, reading documentation, or troubleshooting my own tools — not billed. The first 30 minutes of any engagement are free.

Retainer or pay per project?

Discrete job, defined scope — use the formula; you pay once, after delivery. A MikroTik estate with recurring changes, a topology I retain between months — the retainer. The $420 is the same 4-hour formula price; the premium buys priority and a context I never reload. It is not cheaper per hour. It is faster to answer and skips the first-hour context load. Discrete work uses the formula. Ongoing infrastructure uses the retainer.

Get in touch

Message me on any channel from the contact page. It starts with a free 30-minute call; I book you a day or two out, and you pay only after I deliver.

Contact

Email · Signal · Telegram · Threema · WhatsApp

Billing mechanics

Productive hours accumulate within a billing cycle — invoiced once at close, not per session.

Each hour earns 2 days of context reservation (max 14 days).

A billing cycle closes when work completes or when idle time exceeds the earned context window (hours × 2 days, max 14).

Concentrated work amortizes the context load — fewer cycles, and the sublinear formula delivers a lower effective rate.

Insight: Spreading 12 hours across six separate cycles costs 71% more than one sprint — that’s the real cost of six context reloads.

Terms

Working hours: 10:00–20:00 GMT+7 (Vietnam)
Advance booking: 1–2 days appreciated
Payment: 100% post-delivery, no deposits
Billing: Half-hour granularity, productive hours only
Crypto (USDT): −15% discount
Contact: Email or messenger, your choice