Kirsantov.
enrufr
engagements

Hourly · Project-based · Fractional.

Pricing depends on scope and engagement format — a scoped feature and rescuing a stalled AI architecture don't cost the same hour. We agree the number after we've talked through the task.

Hourly
billinghourly, by the taskscope-dependent · remote

Hourly

For work you can already describe.

A feature, an integration, a fix, a piece of a bigger system. I bill by the hour, you see exactly where the time goes, and we check in as often as the work needs.

good fit when
  • The task is well-defined enough to start without a discovery phase
  • You need senior engineering hands, not a strategy conversation
  • Scope may shift, and hourly billing is the honest way to handle that

starts withA short call to scope the task and agree an hourly rate.

Project-based
billingfixed project feeweeks, depending on scope · remote or your infra

Project-based

An idea or a problem, turned into working software.

For work that starts from an idea, a broken prototype, or a problem you're not sure how to solve yet. We talk it through, I ask the questions that turn it into scope and architecture, then I build it — prototype through production, depending on what's actually needed. If software isn't the right answer, I'll say so before you pay for a build.

you leave with
  • A working system your stakeholders can use, not a slide about one
  • Source code, deployment, and a handover session with your team
  • Architecture documented well enough for another engineer to pick up
  • A price and timeline agreed before the build starts, not after

honest scopePricing is set per project after scoping — no two projects cost the same.

Fractional
billingmonthly retainerpart-time · ongoing

Fractional

Senior engineering, added to your team part-time.

A fixed number of hours a week, month to month, without a full-time hire. Architecture decisions, code review, unblocking what's stuck, keeping direction as the team ships — the role, not just the hours. Also where stalled AI prototypes get picked up and turned into real products.

you leave with
  • Architecture ownership: decisions made, documented, defended
  • Team enablement — your engineers build, I keep the direction
  • Drifted systems brought back: legacy, stuck delivery, unclear design
  • A senior hand on call, without the overhead of a full-time role

who this fitsTeams past the prototype stage, or a team that needs a senior hand for a defined chunk of time each week.

Not a fit

Some things I don't do, so we both save time: thin interfaces over a cloud chatbot API — if your data can go to a SaaS, use the SaaS; scraping and mass cold outreach; and projects that need the word AI more than they need the result.

next step

Describe the task

Get in touchA few lines by email or Telegram is enough to start. If it looks like something I can help with, we'll book an hour on Meet.