Fitzin It LLC develops AI-enabled decision support, automation, and analytics for defense logistics, sustainment and readiness, intelligence workflows, and engineering program support. We scope to the requirement rather than to a fixed product — and we are led by someone who has sat on the government side of these problems.
Most small AI vendors lead with a stack. The result is a solution looking for a requirement, and a team that has to be taught the mission before it can be useful.
We work the other direction. Our leadership has served in the staffs and commands that generate these requirements — writing orders, running an expeditionary district, producing recurring intelligence, and bringing program offices into compliance across five countries. We know what a usable product looks like to the person receiving it, because we have been the person receiving it.
The technology follows from that. AI/ML, data integration, automation, analytics — whichever combination the requirement actually calls for.
Built for the prototype pathway. We are structured for SBIR, BAA, and other transaction awards: small, technically led, fast to a working artifact, and able to team where added engineering depth is warranted.
Prime or subcontractor. We bring domain expertise, socioeconomic status, and real technical work share — not a pass-through.
These are the areas where our leadership has operational experience, so requirements analysis starts from understanding rather than from a discovery phase billed to the government.
Supplier vetting and sourcing risk, trade-agreement compliance, foreign-ownership and control exposure, and the data problems underneath materiel decisions.
Integrating siloed inventory, maintenance, and logistics data; synchronizing schedules across echelons; building a defensible cross-platform readiness picture.
Recurring intelligence production, order and annex drafting, watch-floor reporting, and the analyst workflows that consume most of a staff's available hours.
Program compliance, antiterrorism and protection planning, budget and staff oversight, and the reporting burden carried by dispersed program offices.
Two lanes, one underlying pattern: take unstructured or siloed inputs, ground them against authoritative sources, and emit something a human can act on and defend.
SBIR, BAA, and other transaction prototype vehicles, where technical merit and speed to a working artifact matter more than a long past-performance record.
We bring four socioeconomic eligibilities in one entity, defense domain expertise, and real technical work share to teams that need both.
We maintain a working prototype in the commercial services market that demonstrates our core technical pattern end to end. It is not a fielded government system and we do not present it as one — it is a demonstrable reference implementation we can walk an evaluator through.
An inbound request arrives unstructured over voice. The system captures it, grounds it against an authoritative knowledge base and public property records, and delivers a structured brief to the responding technician before dispatch — equipment context, likely fault, and what to bring.
That pattern is domain-independent. The commercial instance briefs a service technician. The same architecture briefs a maintainer, a watch officer, or a program analyst — the authoritative data changes, the compliance envelope changes, the pattern does not.
Founder-led by a cleared Army veteran with deployed staff and command experience and a PMP. We write to the requirement because we have written the requirement.
EDWOSB, WOSB, SDVOSB, and VOSB in a single small business — a clean fit for socioeconomic goaling and subcontracting plan credit without assembling a team to get there.
A working prototype demonstrates our technical pattern today. Concepts we submit are backed by something we have actually stood up, not by a reference architecture diagram.
Small enough to move at prototype speed, with an established teaming relationship supplying additional AI engineering bench when scope demands it.
Concepts developed and submitted to the Defense Logistics Agency, the Naval Aviation Enterprise, Army Cyber Command, a Department of War logistics customer, and the National Science Foundation — capability evidence, not a claim of prior contract performance. Detail is in the capability statement (PDF).
Cleared Army veteran and mom of five. Seventeen-plus years of service across tactical intelligence, division and expeditionary staff, and program oversight — including service as Deputy Commander of a forward-deployed engineer district and as a division antiterrorism officer responsible for bringing subordinate districts across five countries into compliance. Currently completing a Doctor of Engineering in AI/ML.
The through-line is the same one the work is built on: taking scattered, low-quality inputs and producing something a decision-maker can actually use, under time pressure, with the sourcing intact.
Sources sought, RFI responses, capability briefings, and teaming inquiries welcome. We respond to every one.