Scroll ↓

Elizabeth Fulgham

I turn ambiguous business problems into reliable software systems.

systems architectsoftware engineerintegrationsAPIsLLM systems
weeks by hand
→ ~20 min
→ 6–10 min
About 100 model calls
and $3 per scan
SSRF and DNS-rebinding
defence in the crawler
Deterministic scoring, kept separate
from model output
No. 1 · Internal platform · 2025–26

BIOS

A brand assessment that took weeks by hand, rebuilt as a multi-LLM platform.

Read the case study →
two-line brief
→ client-ready in 14 days
SuiteCRM is the only store.
WordPress persists nothing.
Whether a quote won is derived,
never stored
identity from the session,
never the payload
No. 2 · Client · 2026

QuoteDesk

An open-ended client need turned into a quoting system spanning WordPress and SuiteCRM.

Read the case study →
five plugins · one LMS
Dry-run remediation tooling
for live completion state
requirements changed
after estimates
A 95-hour estimate that moved
the account to hourly billing
No. 3 · Client · 2024–26

Learning & Engagement Platform

Onboarding, progression, activities and reporting, under requirements that kept moving.

Read the case study →
no servers, no budget:
built on Google Workspace
The database is a spreadsheet,
on purpose
Every release diffs against
a snapshot and logs what changed
PDF rendered onto a fixed
46-row paper form
No. 4 · Prototype · 2026

Process Documents

A manufacturing process document system with a gated release workflow, built entirely on the tools a small team already had.

Read the case study →
About

I design and build software systems end to end: data model, backend, integrations, security, and the interface people actually use. Most of my work starts as a sentence rather than a specification.

I'm usually brought in when several systems that were never meant to talk to each other now have to.

2022 · Web Operations2023 · Web Developer2024 · Project Manager2025 · Systems Architect
Elizabeth Fulgham

Say hello.

EmailLinkedInRésumé
Elizabeth Fulgham · Hickory, NC · · Nothing for sale.