Garnet CourtSoftware studio

What we build, and what we look after

Four kinds of job.

  • Custom business systems

    Order handling, scheduling, internal portals and reporting: the software your staff use all day, where no product on the market quite fits.

    You get
    Tests and documentation with every release.
    We need from you
    Someone who can decide, and a few of the people who will use it.
    How long
    Eight to twenty weeks to a first release.

  • Integrations

    We connect the systems you already pay for: finance, stock, the CRM, a supplier's portal.

    You get
    The connection, an alert when it fails and a page showing what went through.
    We need from you
    Access to both sides, and someone who knows how the data should line up.
    How long
    Four to ten weeks.

  • Data migrations

    We move you from the old system to the new one in a rehearsed cutover. We check the new data against the old until the totals match.

    You get
    A rehearsed cutover and a report of every record that did not match.
    We need from you
    A copy of the old data, and the person who knows where it is untidy.
    How long
    Six to twelve weeks, depending on the state of the old data.

  • Takeovers and rescues

    Somebody else wrote it and nobody understands it now. We read it, write down what it does, fix what is dangerous and tell you whether to keep it.

    You get
    A written assessment first, then fixes in order of risk.
    We need from you
    The code, the servers it runs on and an hour with anyone who remembers it.
    How long
    The assessment takes two weeks.

A project, from brief to handover

  1. A brief, then a call

    You fill in the brief. We read it before we talk, so the thirty-minute call covers the open questions.

  2. A written estimate

    Two or three pages on what we will build and what we assumed. Your finance team can read it without us in the room.

  3. Two-week cycles

    Each cycle ends with something running that you can use. You can see the repository and the task board from day one.

  4. Handover

    You get a runbook for whoever looks after the system. Thirty days of fixes follow. A monthly retainer is available.

0007-billing-email.sqlOne step of a migration.
BEGIN;

ALTER TABLE customer
  ADD COLUMN billing_email text;

UPDATE customer
SET billing_email = email
WHERE billing_email IS NULL;

ALTER TABLE customer
  ALTER COLUMN billing_email
  SET NOT NULL;

COMMIT;

Have a system in mind?

Describe your project