Systemcraft Inquire
Systemcraft · Phoenix, Arizona

Tell me the part of the week you dread.

It is almost never the work. It is everything around the work — and that is the whole of what I build.

Your week, as it stands.

Click the blocks that are yours. The diagram routes what you hand over — nothing here is claimed, it is counted.

Routing
0 of 12 blocks routed

Every line comes from a block you hand over. The page has no opinion until you give it one.

What runs instead

    Nothing yet. Every line here comes from a block you hand over — the page has no opinion until you give it one.

    01

    Two kinds of business, one missing thing.

    A working desk in daylight: a ring-bound notebook, loose invoices, a pen and a mug.
    No systems yet

    Small businesses running on memory

    The owner is the system. It works until they're out for a week. We start from scratch and build only what earns its place.

    Systems already

    Teams whose stack has outgrown them

    The tools exist and don't talk. The same work is re-entered by hand three times. I service, connect and extend what's there rather than replacing it.

    02

    What I build.

    Sundial

    Booking & scheduling SaaS

    A scheduling product for businesses whose storefront is a calendar — and for mobile vendors whose storefront is a pin on a map. Customers find who's open near them; operators go live in one tap.

    Built end to end: the availability model, a real coordinate-to-map projection for radius search, calendar file export, and an admin side for live location.

    Next.jsPostgres · PostGIS Row-level securityDesign system
    The Sundial home page: a search for local services with live availability.
    Running the shipped app

    Galactic Command Center

    Multi-agent operations system

    A private operations system where a roster of specialist agents debate a decision, audit their own output and file the result — running across a hosting node and a compute node with local models.

    The interesting part isn't the agents, it's the gate: an automated check rejects any figure an agent can't source. That is the difference between an AI system you can act on and one you have to double-check.

    Node servicesLocal model routing Voice I/OOutput-quality gates
    AGENTS MODERATOR GATE FILED
    △ Private system — diagram, not a screenshot
    03

    Four steps, and you own it at the end.

    Sorted paperwork on a pale desk: separate stacks of documents, pencils and a clip.
    01

    Map

    A working session and a walkthrough of how the job actually gets done — not how the org chart says it does.

    02

    Cut

    We pick the one block worth automating first. Usually the one someone re-types by hand.

    03

    Build

    Short cycles, something running you can look at, no six-week silences.

    04

    Hand over

    It ships with the documentation and the access. You own it — including the option to never call me again.

    04

    Who you work with.

    Gorgeluis Guillen Martinez

    Systems engineer who ships end to end

    You work with me directly. There's no account manager, no bench, and nothing gets handed to someone junior after the pitch — which is the honest trade for not being an agency: you get the person who builds it, and one at a time.

    Contact

    Start with the worst block.

    One conversation, no deck. If there's nothing worth automating I'll tell you that instead.

    hello@systemcraftllc.com
    A corner of a small office in daylight: two chairs at a table, folders and loose paper.