DayLight Creative Technologies

What actually changed.

Two long engagements. What I found, what got built, and what it did for the business, including the parts that did not go to plan.

Both companies are unnamed here at their discretion. I'll tell you who they are on a call, and one of them will take yours.

Emergency hazmat response, East Texas · Seven years

A binder, a spreadsheet and a paging app became one system.

I knew nothing about hazmat response when I started, so the first thing I did was go learn it. What came out of that was one platform on iOS, Android and web, and a billing cycle that stopped waiting on someone's drive back to a filing cabinet.

The part I would rather tell you about is how I knew it had landed, which was not a usage report.

Over Steven Day's shoulder as an office administrator points out something on her screen
Heavy equipment rental and sales · Over seven years

One department made it work. The rest of the company never picked it up.

In parts and purchasing, where someone wanted it to work, it took over the daily work and still runs it. Elsewhere it went quiet.

I publish this one with the failure attached, because that half is the more useful half and some of it is mine.

Also, over eight years

Agency partner work

Eight years as the technical hand behind a creative agency's client work: the person brought in when a project needed someone who could talk to the client and then go build it.

Sites and infrastructure

Builds, migrations and rescues across publishing, healthcare, law, tourism and home services. Including a 290-post, 8,600-image publication migration, server migrations, and zero-downtime DNS and email moves.

Product

A consumer app built and shipped by a two-person company across iOS and Android. Proof that the build side is real, not theoretical.

The long version of either one

Both written out in full, including the parts that did not work. Or ask me on a call and I'll tell you what went wrong too.