Dmitry Parshin, automation engineer

I build the automations that run the repetitive half of your business.

Supplier invoices land in Xero as drafts, and every enquiry gets a reply and a CRM record within seconds. I design these systems, build them on your own accounts and hand them over with documentation.

A demo workspace with illustrative runs. The workflows are modelled on real client builds.

Orbient, operations5 workflows running
Lead intakeTrigger: new WhatsApp message
WhatsApptriggerFWeb formtriggerGmailtrigger{ }Dedupestore onceAIAI qualifyconfidence 0.93HubSpotnew deal, urgentReplysent to customer#Slackon-call notified
Lead intakefinished in 7.3 sall steps succeeded
Lead intakeTrigger: new WhatsApp message
Live demo
  1. WhatsApptrigger
  2. { }Dedupestore once
  3. AIAI qualifyconfidence 0.93
  4. HubSpotnew deal, urgent
  5. Replysent to customer
  6. #Slackon-call notified
  7. HubSpot, new deal
    Sarah, burst pipe
    UrgentRichmond

finished in 7.3 sall steps succeeded

Dmitry Parshin

Hi, I’m Dmitry.

I’m a backend engineer. I wrote Go services for a retail chain at 2 Nabiji, then worked on security-focused software at Check Point, and was part of the team that launched a virtual card product in fintech.

These days I build automations for small and mid-sized businesses. I usually start with whichever process costs the team the most hours each week, automate it fully, and hand it over with a runbook the next developer could follow.

I work remotely from Da Nang, Vietnam, with clients in different time zones. Plans, decisions and progress are written down, so nobody has to wait for a call.

Four of my systems run as public demos.

Paste a real message, invoice or question into any of them and watch what each step does. Each one links to a write-up covering the architecture and the parts that failed on the first attempt.

Lead intake

Qualifies an enquiry, replies to the customer and creates the CRM record. The reference run takes 7.3 seconds from form to HubSpot.

Support desk

Answers from your own policy documents and shows the source, in about 2.6 seconds in the reference build. Questions it can’t answer go to a person.

Documents

Reads emails and PDF invoices and turns them into records in Xero or a CRM.

Reporting

Pulls numbers from email, sheets and the CRM into one weekly view. In the reference model it saves about 44 hours a month.

What automation usually changes

These are published industry figures, not results from my clients. My client work is under NDA, so these are the benchmarks I plan and measure against.

Client projects

These are under NDA, so I describe the process rather than the client.

ProcessIndustryBuilt with
Patient booking, end to endAsks about the problem, offers a doctor, books, reminds and confirms.Healthcare
WhatsAppTelegramClinic CRMAI step
AI voice receptionistAnswers calls, books into the CRM, transfers to staff.Healthcare
PhoneAI stepClinic CRM
Booking and crew dispatchRe-offers the job to another crew when one declines.Home services
TelegramGoogle CalendarSMS
Workshop bookingsService requests and customer notifications.Automotive
Web formHubSpotSMS
Virtual card platformPart of the team that launched cards with Apple Pay and Google Pay.Fintech
PostgreSQLStripe
AI operations over MCPLets a team change and fix automations in plain language.Internal tools
Clauden8n
Patient booking, end to endHealthcare

Asks about the problem, offers a doctor, books, reminds and confirms.

WhatsAppTelegramClinic CRMAI step
Healthcare
AI voice receptionistHealthcare

Answers calls, books into the CRM, transfers to staff.

PhoneAI stepClinic CRM
Healthcare
Booking and crew dispatchHome services

Re-offers the job to another crew when one declines.

TelegramGoogle CalendarSMS
Home services
Workshop bookingsAutomotive

Service requests and customer notifications.

Web formHubSpotSMS
Automotive
Virtual card platformFintech

Part of the team that launched cards with Apple Pay and Google Pay.

PostgreSQLStripe
AI operations over MCPInternal tools

Lets a team change and fix automations in plain language.

Clauden8n

What happens when something breaks

Automations usually fail quietly. An API changes, a token expires, and nobody notices for a week. Every system I hand over is built to make failures loud and recoverable, and you can watch one happen in the console at the top of this page.

Simulate an outage
  • Failed writes are retriedIf the CRM or Xero is down, the record waits in a queue and is sent once the service is back.
  • A named person is alertedBy SMS or Slack, as soon as data stops arriving or a step fails.
  • Unclear cases go to a personAnything below the confidence threshold is sent for review with the full context attached.
  • Every step is loggedYou can see what the system did with any request, and why.

Tools I use most

Most tools with an API can be connected. If yours isn’t listed, ask.

  • n8nWorkflow engine for most builds, cloud or self-hosted
  • HubSpotCreating and deduplicating contacts and deals, routing
  • XeroDraft bills and invoices created from emails and PDFs
  • WhatsAppBooking and enquiry assistants on the Business API
  • TelegramBooking bots and internal alerts
  • Google SheetsReport sources and audit logs
  • ClaudeClassification, field extraction and answers with sources
  • PostgreSQLQueues, logs and state for custom services

From the first email to a running system in about two weeks

  1. Day 1

    You describe one process and send a few real examples.

  2. Day 3

    You get a written plan, a three-minute video and a fixed price.

  3. Before any payment

    We agree on examples, expected results and what happens on failure.

  4. About five working days

    I build it on your accounts and test it on real cases.

  5. Handover

    Access, runbook and a video walkthrough, then 14 days of free fixes.

Web apps and websites

When a spreadsheet isn’t enough any more, I build CRMs, admin panels, client portals and websites, from interface to backend.

Jobs this weekCustom CRM, example
JobCustomerCrewStatus
End-of-lease cleanM. EvansCrew CConfirmed
Switchboard upgradeHarbour PtyCrew AQuote sent
Burst pipeS. NguyenOn callToday 7:30
Logbook serviceT. WalshBay 2Booked

Built for how your team works

Handed over with documentation and access. I also join teams working on fintech and payment products.

  • Small internal web toolsfrom $3,900
  • CRMs, client portals and full web appsfrom $6,500
  • MVPs for new products3 to 4 weeks
  • Websites connected to your lead systemfrom $1,450
Discuss a build

Prices

One working workflow

from $1,190

Up to 3 standard integrations, 5 working days

Connected system

from $2,900

Two connected workflows and a simple status view. Larger systems are quoted.

Automation partner

$690/mo

Monitoring of all workflows and up to 3 hours of new work a month

PackagePrice
Written planWhat I would build, the risks, a fixed price and a short videoFree
AuditA map of the current process, where the time goes, and a build plan. The fee is credited against the build.$350
One working workflowOne process, up to 3 standard integrations, standard cases. 5 working days.from $1,190
Automation sprintA complex workflow with custom APIs, exceptions or data migration, or two simple workflowsfrom $2,190
Connected systemTwo connected workflows and a simple status view. Larger systems are quoted.from $2,900
AI voice receptionistAnswers calls, books into your CRM and transfers to staff. Call and AI usage billed at cost.from $1,490 + $190/mo
Maintenance for one workflowMonitoring, fixes and small changes for one workflow$150/mo
Automation partnerMonitoring of all workflows and up to 3 hours of new work a month$690/mo
Website connected to your lead systemA fast site whose forms go straight into your CRM and lead workflowfrom $1,450
Small internal web toolAn admin panel or tool for one team processfrom $3,900
CRM or full web appA custom CRM, client portal or product, from interface to backendfrom $6,500
Work outside the agreed scopeBilled by the hour$95/hour

Every package includes error handling, failure alerts, a runbook and 14 days of free fixes. 50% before we start, 50% after acceptance.

Experience

2026, nowOrbientAutomation and software for small and mid-sized businesses
2025 to 2026Check PointSoftware developer, security-focused development
2023 to 20242 NabijiBackend developer, Go services for a retail chain
EducationMoscow Aviation InstituteEngineering

Questions

What do you need from us?

A short description of the process, three or four real examples of what comes in, and access to the tools involved. Everything else is agreed in writing.

What if the AI gets something wrong?

Every decision has a confidence threshold. Below it, a person decides. Everything is logged, so you can always see what happened and why.

Who owns the code and workflows?

You do. Everything runs on your accounts and is handed over with documentation, a runbook and a video walkthrough.

Where is the system hosted? Can the data stay in our country?

On your own infrastructure or in a cloud region you choose, for example the EU, the US or Australia. Credentials stay in your systems with the minimum access needed.

What if you become unavailable?

The system is documented well enough for another developer to run and change it. Monthly monitoring and support is optional.

Does the time zone get in the way?

I work on UTC+7. With Asia and Australia most of the day overlaps; with Europe and the Americas we agree a short daily window. Everything else happens in writing, so the work keeps moving while you are offline.

Describe one process, and I’ll send you a written plan within 48 hours.

You’ll also get a three-minute video walking through it and a fixed price.

I use these details only to reply to you. Privacy policy