Who runs this
SiegeStack is Scott Allen Willis, working alone. That is stated plainly because it changes what you should expect: you talk to the person who does the work, there is no account layer between you and the build, and there is a ceiling on how much can run at once. It is not an agency and there is no staff roster behind this page.
The background, without the logos
The work is enterprise distribution software: ERPs backed by SQL Server, the reporting built on top of them, and the operations that depend on both. No client or employer is named anywhere on this site, and the case studies remove industry, size, location and figures rather than disguising them. That is a deliberate constraint and it costs this page some persuasiveness — you get the shape of the work instead of a logo wall.
What that has covered:
- ERP reporting and integration. Deep hands-on work in Epicor Prophet 21. Kinetic shares the transferable parts, and that page says so explicitly rather than implying equal depth in both.
- Performance work on SQL Server–backed reporting, where the usual finding is an access-path problem that volume merely made visible.
- Integration and ETL between CRMs, ERPs and everything downstream of them.
- Operations modernization — consolidating onto one system of record, then slotting, order consolidation, purchasing and network replenishment on top of it.
- The operational programmes described under operations modernization: EDI, ERP carve-outs when a facility is acquired, opening and moving sites, quality systems, vendor-managed inventory, inventory accuracy and system selection.
- Audit work on systems already in production — who can actually read your data, what a security header actually permits, and the class of fault that returns no error and reports nothing.
How the work is actually done
Every claim on this site is checked against the primary source before it ships, and the corrections that came out of not doing that are published rather than quietly edited. The same discipline is the deliverable: a refactor arrives with a measured before-and-after rather than an assurance, and a migration reconciles before anything is called finished.
Where no baseline was captured, no percentage is published. That rule costs this site some impressive-looking numbers and it is not going to change.
What is a good fit
- A distribution or manufacturing operation on a SQL Server–backed ERP where reporting is slow, wrong, or trusted by nobody.
- Two systems of record that were supposed to be consolidated years ago.
- A process that runs because one person remembers the order of the steps.
- Something already shipped that nobody has audited — access, delivery, measurement, or a refactor that needs proving.
What is explicitly out of scope
Stated because a page that claims everything is worth nothing:
- No certifications, partnerships, reseller relationships or third-party reviews are claimed. Nothing here is endorsed by a vendor, and no recommendation on this site earns a referral fee.
- Not a staffing firm. This is project work with an agreed scope, not a body to place.
- Platforms outside the ones named. If a system is not described somewhere on this site, assume the experience is not there and ask — the answer will be straight.
Terms
Clients own everything built for them: full source, documentation and deployment instructions. Scope is agreed in writing before work starts. Maintenance and support are included.