Work with me

Three shapes of work for teams whose Django and Postgres systems have outlived their first authors.

Project · 4–12 weeks

SaaS platforms & MVPs

A first version that becomes your production system, not the thing you rebuild in six months.

Email me

What you get

Architecture and data model designed for the product you described, not a template
Django / DRF / FastAPI backend, integrations and async work where they belong
An honest scope conversation before we start — including what does not belong in v1
CI/CD, tests and monitoring from the first deploy, not added later
You work with the engineer who designed the system

Who it's for

Founders shipping a first version they intend to keep.

Project · scoped per system

AI & LLM systems

Agents, assistants and retrieval that hold up under real users — with evaluation, tracing and cost control.

Email me

What you get

Agent and tool design, including human-approval workflows where the stakes need one
Retrieval that is measured, not assumed — hybrid search, reranking, layout-aware chunking
Evaluation: golden datasets, LLM-as-judge regression tests, tracing with Langfuse or LangSmith
Per-tenant token and cost tracking
Guardrails: prompt-injection defence, PII redaction, per-tenant key isolation

Who it's for

Teams adding AI to a product where being wrong has a cost.

Engagement · scoped after a review

Rescue work

A system you can ship from again, with the reasoning written down.

Email me

What you get

A written review of what is actually wrong, with risks ordered by what they cost you
Refactoring the parts that block delivery, not a rewrite by default
Tests around the paths that make money, before anything structural moves
Handover your team can act on

Who it's for

Teams whose Python system has outlived its first authors.

How I work

Every engagement starts from your idea, not a forty-page spec. I would rather spend the first conversation understanding what you are building than reading a document that is already out of date — and if your budget does not match your scope, you will hear it before we start, not halfway through.

From there it is straightforward: I push back on features that do not belong in v1, even when building them would raise the invoice. I flag problems the day I see them, not at the next sprint review. And you work with the engineer who designed your system, not an account manager who relays questions to one.

Read the full version →

Questions before the first call

How do we start?: Tell me what you are building and where it is stuck. If it looks like a fit, we do a 30-minute call — no deck, no pitch, and an honest answer on whether we are the right team. Scope and estimate come after that call, in writing.
Which time zones do you work in?: I work from Ukraine on European hours, with overlap into the US East Coast morning. English C1, Ukrainian native.
Do you sign NDAs?: Yes. NDA work appears here with the client name withheld.
Do you take on existing codebases, or only new builds?: Both. Founders often come six months in, holding code nobody can maintain, no users, and a budget that is mostly gone — that is rescue work, and it starts with a written review rather than a rewrite.
Who actually does the work?: I do the architecture and discovery on every project and stay hands-on for the core and high-risk parts. Flexipy is a senior-only remote team; you work with the engineer who designed your system.

Email me