Maryna K.

I build internal tools in Retool and workflow automations in n8n and Make for teams that still run operations out of spreadsheets and copy-paste. Problems I usually get hired to fix: INTERNAL TOOLS (RETOOL) - Your ops team edits production data straight in the database, or in a Google Sheet someone exports every morning. I build an admin panel on top of your database with role-based access and a log of who changed what. - Support opens Stripe, the CRM and your admin just to answer one customer question. I put everything on one customer screen, and the actions they need (refund, extend a trial) become buttons instead of engineering tickets. - Refunds, discounts and account changes get approved in Slack DMs, and nobody can trace them later. I build an approval queue with roles, limits and full history. - Your engineers keep getting pulled off the product to build back-office screens. I take that work over in Retool, connected to your existing database and APIs. - You already have Retool apps, but they’re slow and nobody wants to touch them. I clean them up: queries firing on every page load, the same logic copied across ten apps, no permissions. AUTOMATIONS (N8N AND MAKE) - Leads from the website, ads and events land in someone’s inbox and get typed into the CRM by hand, or not at all. I route them straight into HubSpot, Pipedrive or Salesforce, enrich them, assign an owner and notify the right person in Slack. - A new client signs and someone spends an hour creating accounts, folders, invoices and welcome emails. I trigger all of it from the signed contract or the first payment. - Invoices and documents arrive as PDFs and someone retypes them into accounting. I extract the data with AI, send anything uncertain to a person for review, and push the rest into QuickBooks or Xero. - Stripe, your CRM and your database disagree about who paid what. I set up sync jobs plus a daily check that flags mismatches. - Your Zapier bill grows every month with volume. I move the workflows to self-hosted n8n, where you pay for a server instead of per task. Make or n8n? Make when your team wants to edit workflows themselves and volume is moderate. n8n when data has to stay on your own servers, when volume makes usage-based pricing expensive, or when the workflow needs real code inside it. When a tool can’t do something out of the box, I write it: custom JavaScript components in Retool, Code nodes and custom API integrations in n8n, small Python services on AWS or Google Cloud. My longest-running project: two years building and maintaining the internal Retool suite for a UK wealthtech company regulated by the FCA. Their non-engineering teams run daily operations in it. Automations usually break quietly, after an API change or an expired token. Mine retry on temporary errors and alert you when something actually fails, so you hear about it before a customer does. Each one comes with a short doc your team can follow. Send me a few lines on the process that eats your team’s time: how it works today and which tools are involved. I’ll tell you which parts are worth automating and roughly what it would take.