← Home

Custom work, quoted before we start

Chatbots, automations and test suites, built by one engineer. Every project is a fixed scope, a fixed price and a fixed timeline, agreed in writing before any work begins.

Tell us about your project

One email. We reply with questions or a plan, not a sales call.

Three packages

Prices are where a typical project starts. Your quote is a fixed number, never an hourly meter.

  • Chatbots

    from $400

    Website or WhatsApp

    Included
    A knowledge base built from your docs or website, an embed widget or a WhatsApp number, a handoff to email or WhatsApp when the bot is unsure, and two weeks of tuning.
    Not included
    Payments and complex integrations.

    WhatsApp message fees are billed by Meta to your own account. We estimate them for you and never add a mark-up.

  • Automations

    from $300

    Between the tools you use

    Included
    One trigger and up to about eight steps, error alerts, written documentation, and 30 days of fixes. Price per workflow, from $300 up to $1,500.
    Not included
    New workflows (each gets its own quote).

    We install n8n on your own server or account and hand it over. It is yours; we do not host it for you.

  • Test suites

    from $800

    Fixed scope, agreed upfront

    Included
    Playwright set up in your repository, 10 to 30 critical-path tests, CI, and a handover session. Priced from $800 up to $2,500.
    Not included
    Manual testing and ongoing maintenance.

    Written by a working QA automation engineer. Your team keeps everything.

How a project starts

  1. You write to us

    Your business, what you want to happen, the tools you use today, roughly how much volume, your budget range and your deadline.

  2. A 20-minute call

    Only if it helps. The call is for cutting scope, not growing it. The result is one paragraph describing the problem.

  3. A one-page proposal

    The problem, the package, what you receive, what is out of scope, the price, the timeline. 50% upfront, 50% on delivery.

  4. Build, then hand over

    Work in steps of a week or less, each ending in a short recorded demo. At the end you get documentation, a recorded walkthrough and the credentials in your own accounts.

You keep everything

Your data and your API accounts stay yours. After handover we hold nothing of yours beyond what an optional care plan needs.

Have a project in mind?

Tell us in a few lines. If it is not a fit we will say so and, where we can, point you somewhere better.

Tell us about your project