[SUPPORT] / Support

The people who built your system answer.

No ticket queue, no account managers, no tier-one script. You write in, and one of the two engineers who built your system writes back. We reply within one working day. If production is down, same working day.

[URGENT] / Production down

Same working day

[STD] / Bugs and breakages

Within 1 working day

[STD] / Changes and questions

Within 2 working days

[INCLUDED] / After launch

Three months of fixes, in the price

Every fixed price includes three months of fixes after launch. If something breaks in that window, you write and we fix it. No clock running, no fresh invoice.

[FIX] / COVERED

What counts as a fix

Bugs, a broken integration, a model or API change that quietly breaks a flow. Anything that used to work and stopped. That's on us for three months, no questions.

[CHANGE] / QUOTED

What counts as a change request

New features, new scope, a workflow you didn't ask for at the start. We're happy to build it. It just gets a fixed quote like any small build, agreed before we start.

Want us iterating past the fix window? There's an ongoing program for teams that want continuous work, month after month.

[CHANNELS] / Three ways to reach us

[01] / METHOD

Email

Best for bugs. Tell us what you did, what you expected and what actually happened, plus a screenshot or the ID of the item that failed. That one habit makes fixes dramatically faster.

[›] anmwashere@gmail.com

[02] / METHOD

Ami, the assistant

The AI assistant on this site. Instant answers about what we do and where things stand, and it hands you to us when a human is the right call. It's an assistant, not a human pretending to be one.

[03] / METHOD

A call

Thirty minutes, scheduled. Best for anything too tangled to type out. We pick it apart together and agree the next step before you hang up.

[PROCESS] / When something breaks

What happens after you hit send

We reproduce it

First we make it break on our side. A bug we can't reproduce is a bug we can't be sure we fixed, so this step comes before anything else.

We ship the fix

Then we fix it and deploy to your accounts. Small breakages usually go out the same day. Anything bigger, we tell you the timeline up front.

We tell you what broke

You get a plain note on what went wrong and why, so it isn't a black box. If it points to something worth hardening, we say so.

[FAQ] / FAQ

Straight answers

One of the two engineers who built your system. No account managers, no first line of support reading from a script. The person replying has your code open.

You can write in and we'll quote the fix, or you can be on the ongoing program and it's already covered. Either way the system is yours and any developer can pick it up, since the code lives in your repo.

Yes. New features and new scope get a fixed quote up front, like any small build. Fixes to what we shipped stay free for three months. We'll always tell you which bucket your request lands in before we start.

Every delivery ships with system documentation, a user guide and a recorded walkthrough. Your team should be able to run the thing day to day without us in the room.

Anything with an API, plus the usual suspects: Slack, HubSpot, Notion, Google Workspace, Shopify. If it exposes a way in, we can connect to it.

Sometimes. We audit it first, then give you an honest yes or no. If the code is a mess we can't stand behind, we'll say so rather than take money to babysit something we don't trust.

EU working hours, async by default. We work in English and Russian. You won't get instant round-the-clock humans, you'll get a real answer within one working day and same working day if production is down.

[Something broken right now?]

Tell us what's wrong.

One message with what broke and when. We'll pick it up within a working day, faster if it's down.