● available for new projects · miami, fl · remote

I build tools that
work. Rules your
team can CHANGE.
Weeks you get
BACK.

When your business is running on spreadsheets and manual work, I'm the person you call. I design and build web applications, CRM systems, calculators, and automation tools. So you can focus on the work that actually matters.

view my work let's talk
what i build
based in miami · working remotely worldwide
Pricing & Quoting

Pricing, quoting and document tools

Rate cards that differ by customer, volume breaks, quote builders, and the paperwork that has to come out matching the quote. The rules live where your team can change them, and anything you would rather price or word by hand stays with a person.

built: a multi-account quote engine, a clause compiler for certificates, a pricing and promotions model across 15,000 SKUs

Automation & Bots

Process automation and Telegram bots

The small repeated things that quietly eat a week: the same email written again, the handoff that depends on someone remembering, the report assembled by hand every Monday. If your team does it more than twice a week, it is usually worth removing.

built: booking alerts and lead capture over Telegram, quote-request emails, document assembly from parameters, scheduled digests

CRM & Booking

CRM and booking systems

Client records, scheduling, forms, payments and reminders, shaped around how you actually work rather than how a SaaS product assumed you would. Worth building when the off-the-shelf options genuinely do not fit, and I will tell you when they do.

built: a full booking and client system for an aesthetic studio, consent forms by QR, Stripe checkout, two-way calendar sync

Reporting

Reporting and analytics

Fifteen years of turning operational mess into numbers someone can act on. Margin and profitability models, monthly reporting that assembles itself, and dashboards that answer a question rather than display everything at once.

built: monthly supplier reporting across imports, depletions, stock and channels, cut from days to hours

what it costs

What a project costs depends on how much of the process has to be worked out before anything gets built, so the first conversation is usually about what the current way of doing it is costing you now. Smaller automations are often a few days. And if what you need is a product you can simply buy, I will say so.

how i work
01
Work out what it should be

Before anything is built I want to see the process as it runs today, including the parts people have stopped noticing. Most of the value turns up here: half of what gets done by hand turns out to be a rule nobody ever wrote down.

02
Decide what not to automate

Some decisions should stay with a person, and a good system says so out loud instead of guessing. Pricing the ordinary cases automatically and routing the awkward ones to someone who can judge them is usually the right split.

03
Build it, and put the rules where you can reach them

Anything that changes with the business belongs in data your team edits, not in code only I can change. That is the difference between a tool you own and a tool you depend on me for. I build with modern AI-assisted tooling, which is why this takes weeks rather than the months an agency quotes.

04
Stay while it settles

The first weeks in real use are when the missing cases appear. I would rather be there for them than hand over a thing that technically works and disappear.

What I take on

I take a process end to end: working out what it should be, designing the tool, building it, and staying on while it settles. Processes that already exist, and the systems already around them, are the normal case rather than a problem.

What I do not do is join an engineering team as an extra pair of hands in a codebase someone else owns. If that is what you need, I am the wrong person and will say so in the first conversation.

selected work
Pricing & Document Automation · in production

The Quoting Desk

freight insurance brokerage · two tools, one workflow

Two tools covering one job. The first prices an enquiry: every customer has their own negotiated rates and their own list of what they can quote on, set in an admin panel rather than in the code. The second assembles the paperwork from the same answers, picking clauses by rule, holding back anything a person should read first. Both work the same way, by keeping the business rules in data the team edits themselves. Neither is specific to insurance.

Next.js 14 JavaScript Supabase Resend Rules Engine Vercel
Read the Case Study ↗ Adapt it to your business
one set of answers, a price and the paperwork
CRM · Booking System

Beauty CRM

built end-to-end for an aesthetic studio

A client-management and booking system built from scratch: appointment calendar, client cards with full history, consent forms delivered by QR, online booking, notifications over Email, SMS and Telegram, Stripe checkout, and a daily revenue dashboard. It replaced a paid booking service the studio could not bend to how it actually works. The subscription stopped, and the settings and client notifications are now the ones they asked for.

React 18 + Vite TypeScript Supabase Stripe Twilio
Case Study
Analytics · Pricing

Pricing & Promotions Engine

MB Group · 15,000+ SKUs · 15 years in production

An analytical tool for a large wine import portfolio. Dynamic price modeling, profitability analysis, and semi-automated monthly reporting across imports, depletions, stock levels, and sales channels. Reduced report generation from days to hours.

Excel / VBA Data Analysis Automation Pricing
Case Study
Website · Telegram Bots

THE LAB

aesthetic studio · Aventura, FL

A whole digital front for one studio: the website built from scratch with its design, content and SEO, plus two Telegram bots behind it that push bookings to staff the moment they land and collect new client contacts. Since launch the studio turns up in search far more often, is increasingly found through AI assistants too, and new clients book themselves instead of being chased.

Next.js Tailwind Telegram Bot API SEO
Live Site ↗
E-commerce · Payments

Ginger Ocean

swimwear shop · built, opening soon

An online shop built through to checkout: catalog with color and size variants, cart, Stripe Checkout, and stock that decrements on the paid webhook rather than on a click. Prices, stock, copy, delivery terms and returns all live in the database, so the owner runs the shop by editing data and never touches the code. The live payment account and the domain are the last step before it opens.

Next.js 16 TypeScript Supabase Stripe
Launching soon

have a process
that needs fixing?

Whether it's a clunky spreadsheet, a manual workflow, or a tool that simply doesn't exist yet. I find the gap and build the solution. Let's talk about your business.

start a conversation
about

analyst.
builder.
problem solver.

Olga Drew

I'm Olga Drew, based in Miami. I spent fifteen years inside the operations of companies that move real things around: a 15,000-SKU catalog, pricing models, the monthly reporting, and the daily back-and-forth between finance, logistics and sales.

For most of those years the answer to a broken process was another spreadsheet, and I built plenty of them. Eventually I got tired of the workarounds and started building the actual tools instead: web apps, internal systems, and the kind of automation that quietly removes a job nobody should be doing by hand.

I work remotely, in English and Russian. I'm most useful in businesses I already understand from the inside: distribution and wholesale, logistics, and the service side of beauty and aesthetics.

tools I build with
React / Next.jsFrontend
TypeScript / JavaScriptLanguage
Node.js / PostgreSQLBackend
Telegram Bot APIAutomation
Excel / VBAAnalytics
Stripe / Twilio / ResendIntegrations
contact

let's
build.

Tell me what isn't working.
I'll tell you what I'd build instead.

open to projects, remote roles, and the occasional interesting detour
Telegram is the fastest way to reach me: usually a few hours, often less

hello@code13.pro Telegram