What we've built

Built by our lead engineer. Names and details are kept general to protect the organizations we work with.

Service shop operations

Problem
A service shop ran on dealership software with no live view of the business, no shared schedule, and printing that fought the browser.
What we built
A live business dashboard for revenue, operating income and work in progress, a full screen service board for the shop's wall TV, and a two way sync between the dealership software and an Outlook calendar, so a change in either place updates the other in the shop's own time zone. Plus a print router with a browser extension and admin settings with a rule builder. Infrastructure as code with separate dev and prod environments, deployed by CI with no stored passwords.
  • .NET
  • Azure Functions
  • Microsoft Graph
  • Bicep
  • TypeScript

Spreadsheet to app

Problem
A team ran its daily operations report from a shared workbook that many people edited every shift.
What we built
A web app with single sign on, role based permissions and a full audit trail. Sensitive data is encrypted in the database, only approved roles can see it, and every view is logged. Report layouts are versioned, so changing the form never breaks old reports.
  • Python
  • Django
  • SQL Server

Integration engine

Problem
Every new data feed between systems meant writing new code.
What we built
A generic engine where each feed and destination is a row in a registry table. Timers stage incoming files, check and load them in one transaction, build outgoing messages and deliver them, and every batch is tracked. Adding an integration is a few rows and two small procedures, with no changes to the engine.
  • Python
  • Azure Functions
  • SQL Server

Account onboarding automation

Problem
New hires, rehires and transfers meant setting up accounts by hand across directory and service desk systems.
What we built
Backend services that create and update user accounts straight from onboarding requests, encrypt personal data stored in tickets, and give the service portal a clean API, plus a role based access model so permissions follow a person's role. Security reviewed end to end, covering safe directory queries, parameterized SQL, strict input validation, and no duplicate actions when a request retries.
  • .NET
  • C#
  • Active Directory

Service desk portal

Problem
Staff worked tickets in a slow, generic portal, and common requests like onboarding a new hire were long manual forms.
What we built
A ticket dashboard rebuilt from one large script into 22 focused modules, guided request forms for new hire onboarding, incident reports and new tickets, and a redesigned staff portal with a service catalog, search across every open and closed ticket, and ticket activity beside the form.
  • JavaScript
  • TypeScript
  • Kendo UI

Clinical and financial reporting

Problem
Quality measures, payment reports and emergency visit coding were assembled by hand from the clinical systems.
What we built
SQL reports and Power BI measures that run straight against the clinical and billing databases, covering quality measures, patient payments, emergency department coding levels and social risk factors.
  • SQL
  • Power BI

Under the hood.

The demo on our home page is a toy. Real projects are built like this, typed, logged, and written to be read by whoever comes after us.

orders/models.py
class Order(models.Model):
    class Status(models.TextChoices):
        NEW = "new", "New"
        PACKING = "packing", "Packing"
        SHIPPED = "shipped", "Shipped"

    number = models.PositiveIntegerField(unique=True)
    customer = models.ForeignKey(Customer, on_delete=models.PROTECT)
    status = models.CharField(max_length=10, choices=Status.choices, default=Status.NEW)
    owner = models.ForeignKey(settings.AUTH_USER_MODEL, on_delete=models.PROTECT)
    history = HistoricalRecords()

    class Meta:
        ordering = ["-number"]

Tell us what you need built.

Get in touch