Derick Howard

Product · systems · operations

I build software for work that cannot stay inside a screen.

Construction documents, legacy workstations, guest operations, and small-business systems. I turn the moving parts into a tool a person can use and a result they can verify.

View selected work Download ATS résumé

Temecula, California · Open to remote and Southern California teams

Derick Howard in a black suit jacket and white shirt
Derick HowardBuilder who moves between code and operations.

The working position

Learn the operation. Build the complete loop. Keep the claim as honest as the evidence.

I am early in my business career, not early in curiosity or shipping. The work below is the clearest explanation of how I think.

Selected work

Real artifacts, fewer claims.

Each project names the operating context, the thing I built, and the boundary on what happened next.

01 / Flagship

Instruxit

From hostile plan sets to an estimator-reviewed, source-linked bid package.

Open instruxit.com
Input
PDF plan sets, specifications, addenda, and scope decisions
Built
Review cockpit, structured .bid package, and human approval path
Observed
Hands-on assembly fell from roughly 40 hours to about 5 in one real bid cycle*
  1. Current Instruxit main site showing its Millwork and Casework Estimating product cover
    01

    Main site

    The public product front door and the cover for this case study.

    Visit site
  2. 02

    Scope view, working

    Fourteen seconds from plan page to source-linked room scope.

  3. Authenticated Instruxit production cockpit showing a real plan review and a redacted dot-bid package status inset
    Authenticated production capture. Client identifiers and filesystem details are redacted.
    03

    Real Cockpit and .bid package

    A production bid moving through page selection and traceable package status.

*Observed, not guaranteed: the 40-to-5 comparison comes from one bid workflow, not a controlled benchmark. Instruxit was built collaboratively; Ken contributed substantial development and domain iteration, and high-impact decisions remained human-reviewed.

More selected work

A short project index.

FIELD Legacy KDS Field WatchA passive Windows 8 watcher that alerts the owner without interrupting the restaurant display. Paid onsite deployment WEB + MOBILE Everything StevensA React and Expo owner preview verified across 24 routes and Android API 28 through 36. Independent owner preview PHYSICAL + DIGITAL Horizon Haven / AltonBnbI helped rebuild the house, then connected direct booking and channel operations. Operating property BUSINESS SYSTEMS BetterBisMy operating lab for websites, communications, CRM, and launch systems for local businesses. Operating platform

How I work

Three moves, repeated.

AI is in the toolchain. Judgment, privacy, and final decisions stay human.

  1. 01

    Get close to the operation

    Learn the room, screen, estimator, property, customer, or constraint before choosing the tool.

  2. 02

    Build the complete loop

    Connect a real input to a useful output instead of stopping at a polished mockup.

  3. 03

    Verify the result

    Use tests, rendered screens, public links, and explicit boundaries. Prose alone is not proof.

Contact

Bring me the workflow everyone works around.

I am looking for a team where software has to connect to people, operations, media, or physical systems.

Email Derick Connect on LinkedIn Download ATS résumé
QR code that opens derick-howard.com
Scan to open this site.Keep the QR for a résumé, card, or event.
Download PNG Download SVG