Taking on new automation projects
I build the automations, CRMs and data pipelines that take copy-paste work off your team, so their hours go back to clients and sales.
Describe one task. Get a written plan and a fixed quote within one business day.
See every step that runs without anyone touching it.
Running…
Pick the one that sounds like your team. Here’s what it looks like once it runs on its own.
Most of my work sits between the tools a company already pays for. I connect them, clean up the data moving through them, and build the missing pieces when no tool fits.
Contracts, payments, bookings and reports that move themselves. A signed contract opens the client channel, sends the invites and emails the right rep before anyone has to remember.
When the spreadsheet has 100,000 rows and fifty people editing it, it’s time for a real database. I migrate the data, keep the old sheet running in parallel, and give each person a screen made for their job.
Scrapers, browser extensions and enrichment jobs that turn listing sites and public records into clean, deduplicated, ready-to-call lists.
Agents that research markets for you, and pipelines that pull every sales call, transcribe it, summarize it and file it where managers will actually read it.
Built for a fast-growing real estate and short-term rental operations company. Client details stay private; the numbers are real.
The team was dialing the same houses twice because one property was listed on three sites. I moved everything into a database, collapsed cross-platform duplicates into about 69,000 real properties, and gave every caller their own PIN-protected queue.
Built with Supabase, Streamlit, FastAPI, Python
Migrated the client tracker off a project-management board into a proper database, imported 900+ historical payments from two processors, and added a call log for account managers and a portal clients can log into.
Built with Supabase, Retool, Flask, PostgreSQL
When a contract is signed, the client gets a private Slack channel, an invite to the community and a personal intro email from their assigned rep, sent from the rep’s own address.
Built with Zapier, PandaDoc, Slack, Gmail send-as aliases
Payments from several checkout and financing providers land in one sheet with the right processor name, and disputes trigger an instant alert that tags the people who handle them.
Built with Zapier, webhooks, Google Sheets, Slack
Callers browse listings as usual; one click saves the property, contact and price straight into the CRM’s import queue, where it gets deduplicated before anyone dials.
Built with Chrome extension APIs, JavaScript, Supabase
Mobile-friendly scraper apps for map listings and rental sites, plus enrichment jobs that find decision-makers and contact details for brand outreach.
Built with Python, Chrome DevTools Protocol, residential proxies, Docker, Render
Recordings and transcripts arrive in a searchable log each morning. Meeting summaries post straight to the right team channel, translated when a manager prefers another language.
Built with Zoom API, GitHub Actions, Supabase, Streamlit, Zapier
An AI agent that researches a city for rental arbitrage: typical rents, nightly rates, occupancy and local rules, then writes it up as a brief the sales team can use.
Built with Claude Agent SDK, Python
Reps post their end-of-day numbers in Slack or Telegram the way they always have. A listener reads each message, matches it to the right person and writes clean rows to the team sheet.
Built with Zapier, Telegram bots, regex parsing, Google Sheets
Each new deal post carries a claim link. Account managers fill a short form, the claim is logged privately, and the same deal can’t be claimed twice.
Built with Telegram Bot API, Google Apps Script
Think of one repetitive task: copying payments into a sheet, posting reminders, sorting leads. Set the sliders and see what a year of it adds up to.
624hours a year you could offload
That’s about 16 full work weeks spent on one task.
Small enough to start this week, structured enough that nothing breaks on the way.
A short call where you walk me through the task as it happens today. I write back a plain-language plan: what will run automatically, what still needs a person, and what it costs.
I build next to what you already use, so nothing stops while it’s tested. You see it working on real data before anything is switched over.
You get short video walkthroughs, documented logins and a fix window after launch. If something in your tools changes later, I’m a message away.
Every project starts with a free written plan, so you know the scope and the price before anything is built.
A single task automated end to end, like payment tracking, onboarding or daily reports.
A CRM, internal tool or data pipeline that replaces an overloaded spreadsheet.
A monthly retainer for teams that keep finding new things to automate.
If your team already uses it, I can probably connect it.
Zapier, webhooks, Google Apps Script, Slack Workflows, Telegram bots, Typeform, PandaDoc, Monday.com
Python, PostgreSQL, Supabase, FastAPI, Flask, SQLite, Docker, GitHub Actions, Render
Retool, Streamlit, HTML and JavaScript, Chrome extensions, Google Sheets dashboards
Playwright, Chrome DevTools Protocol, proxies, Zoom API, Claude Agent SDK, Anthropic API
The things most teams ask on the first call.
No. I build on what you already pay for, and only suggest something new when your current setup can’t do the job.
You do. Everything runs in your own accounts, and you get documented logins and a video walkthrough at handoff.
Every delivery includes a fix window after launch. After that, small fixes are quick to quote, or a monthly retainer covers them.
Async by default over Slack, email or Telegram, with calls when they help. My working hours overlap US business hours.
Your written plan includes a fixed quote before any work starts. Retainers are a set monthly amount for a set block of hours.
Describe the task in your own words. You’ll get a reply within one business day with questions or a first plan.