All insights
    Engineering10 July 2026· 4 min read· by Christoph-Thomas Abs

    Two systems, one deploy: our setup for safe iteration

    How a separated live and test system — combined with Claude Code and a GitHub pipeline — makes fast iteration possible without putting production at risk.

    ENGINEERING
    Two systems, one deploy: our setup for safe iteration
    ReachOutSoftwareInsights · reachout.software

    Speed and stability are supposed to be opposites. In our setup they are not.

    The key: two separate systems, one shared foundation.

    You work on the live system every day, with your team and your customers. Alongside it sits a protected test system that only you and we can reach — wired to Claude Code and a GitHub repo with a continuous deployment pipeline.

    That lets you try out content and front-end ideas yourself, by prompt. Every change comes to us as a ticket, gets reviewed, and is rebuilt properly in the backend. Deploying is done by us and only by us — that is what keeps production stable.

    The result: changes go live in minutes instead of weeks, without the risk of breaking the running system.

    Christoph-Thomas Abs
    Christoph-Thomas Abs
    Technische Leitung · ReachOut Software
    Connect on LinkedIn
    How many sprints does this take?

    From topic to scope — transparent, in a sprint.

    We translate a topic like this into concrete tickets with estimated hours. Usually one to two 14-day sprints — predictable, cancellable at any time, every hour visible on the Kanban board.

    Setup & architectureBuild the core featureSecurity & reviewGo-live
    Go-to-market

    Software without market entry stays code.

    For go-to-market we recommend our sister company Prometheus Marketing – same Kudamm, same sprint rhythm. ABM target lists, LinkedIn & Microsoft ads, outbound: your first customers and partners.

    Prometheus Marketing