Code Shack Labs
Sheet A-3

Work

Tools in daily use, described the way we would describe them to a colleague. Client names appear only with permission, so some are identified by industry.

Client
A specialty pharmaceutical developer in the Research Triangle, North Carolina
Service
Data formatting and reporting
Delivered
2026
Stack
Plain HTML, CSS, and JavaScript. No build step, no server, no dependencies to install.
A-3.1

FDA submission formatter for a pharmaceutical lab

The problem

In vitro release testing produces long-format spreadsheets from the bench: one row per cell, per time point, per run. The FDA wants the same data in a specific SAS transport layout described on a single page of a guidance document. For every pivotal and validation study, an analyst was reshaping those workbooks by hand, then checking them by hand, then hoping.

What we built

A browser tool with two pages, because the two kinds of study start differently. The pivotal page takes one workbook with a blinded test and a blinded reference. The validation page takes one workbook per run, for repeatability, discrimination, and robustness, all at once. Both pages run the same pivot and the same checks, so the output layout is identical and any error is named with its row and reason.

  • Reads the lab's own export format directly, no re-keying
  • Produces the required layout as a download, ready for the submission package
  • Flags missing time points, mismatched labels, and out-of-range values before they reach a reviewer
  • Ships with test workbooks and expected outputs so QA can verify it independently

The offline guarantee

Release data is confidential, so the tool was designed to make no network requests at all. Spreadsheets are read by the browser's own file reader, pivoted in memory, and rendered locally. The only thing that leaves the tab is the file the analyst chooses to download. A content security policy in the page enforces it, and the same four files can be copied to a shared drive and opened with no server in the picture.

Source is available for review on request, so colleagues, QA, or IT can satisfy themselves about exactly what the tool does.

Client
Code Shack Labs
Service
Internal tools and workflows
Delivered
2026
Stack
Plain HTML, CSS, and JavaScript. Data stays in the browser, with export and import for backup.
A-3.2

Quote builder for our own shop

The problem

Every engagement begins with a written quote, and quotes drift. Line items get retyped, terms get paraphrased, and a customer's payment terms from last time have to be looked up. We wanted a tool that made the consistent thing the easy thing, and we wanted to build it exactly the way we build for clients.

What we built

A single-page quoting tool with an edit view and a print-ready preview. It keeps a list of saved customers with their terms, a library of reusable line items, and a standard list of deductions that can be applied per line. Discounts and tax are handled in the totals. The output prints to a clean one-page PDF with signature lines for acceptance.

  • Saved customers and reusable items, so the second quote takes minutes
  • Standard deductions that can be applied, or shown and cancelled out, on any line
  • Backup and restore as a single file you keep with your own records
  • No server and no account, so there is nothing to maintain and nothing to breach

Why it is on this page

Because it is honest evidence of how we work. The same care, the same plain stack, and the same handover documentation we give clients, applied to the tool that produces your quote.

Want a walkthrough?

We are happy to show either tool on a call and talk through how the same approach would apply to your work.

Get in touch