Veteran-founded · Workflow automation for small teams
Stop refreshing the portal. Let the changes come to you.
We build small, quiet tools that watch the systems your team already uses, notice what changed, and tell the right person. Spreadsheets become real databases. Portals stop needing a babysitter. The inbox only gets what matters.
38.8339° N · 104.8214° W · COLORADO SPRINGS
Sound familiar?
Good people, stuck doing a computer's job.
01
Checking by hand, all day
Someone logs in to a vendor or customer portal again and again, just to see if anything moved. Most checks find nothing. The one that matters gets missed at 4:55 PM.
02
The spreadsheet that runs the company
Years of orders and customers live in one workbook. It works until two people edit it at once, or someone needs an answer the columns were never built for.
03
Status updates by copy and paste
Order status, shipment ETAs and service tickets live in three different places. Every customer email starts with ten minutes of looking things up.
Example fix
In designThe work-order watcher: one quiet helper, fewer missed changes.
An equipment supplier handles warranty service for its customers. Work orders arrive through a service portal, and one operations manager tracks every one of them by hand. Here is the fix we designed.
Before · a typical day
- 7:10 AMLogs in to the portal. Scrolls the list. Writes down two new work orders.
- 9:40 AMChecks again between calls. Nothing new. Checks the shipment tracker in another tab.
- 1:25 PMA technician moved an ETA back two days. Nobody told her.
- 3:50 PMA customer calls asking why the repair is late. She finds out on the phone.
After · the design
- 6:30 AMOne digest email: what changed overnight, sorted by urgency.
- Every 15 minThe helper checks the portal for her. Most runs are silent, by design.
- 1:26 PMAlert: "ETA moved two days." She emails the customer first.
- Any timeA bookmarked "Check now" button: "Checked at 2:14 PM · 3 changes."
How it works
- CheckEvery 15 minutes, or on demand, pull the work orders updated today.
- CompareFingerprint status, ETA, priority and notes. Keep only what changed.
- DecideHer rules sort each change: alert now, morning digest, or ignore.
- RecordEvery change is saved with a timestamp, so history is one search away.
15 min
Longest a change can wait before she hears about it. The design target.
Read-only first
Two weeks of watching before the tool is allowed to change anything.
Measured, not promised
Time saved gets measured during the pilot and posted here only once it's real.
How we work
Map it first. Then build the smallest thing that helps.
STEP 1
Sit with the workflow
We watch how the work really happens, write it down, and agree on the one change worth making first.
STEP 2
Build small, on your terms
One focused tool, in an account you control, with a monthly cost you see before we start.
STEP 3
Run it safely
Read-only first, least-privilege access, secrets locked away, and a clear way to switch it off.
STEP 4
Hand it over
Plain-English docs, a cost estimate, and a decision record, so nothing depends on us remembering.
Under the hood: cloud architecture on AWS, API integrations, data migration from spreadsheets, CI/CD pipelines, and the networks it all runs on.
Built in public: starting January 2027, we'll share what we build and what breaks on our series, The Build Log.
Team
Two engineers. You talk to both.
Veteran-founded. One designs the network and architecture underneath; the other ships, automates and secures what runs on top.
Nelson Walker
Co-founder · Cloud and network architecture
Fourteen years in the U.S. Air Force integrating and testing command-and-control systems that had to work together the first time. At Strike Logix he designs the architecture and networks underneath every build, and turns messy workflows into small, well-documented automations.
AWS Solutions Architect Associate · AWS Cloud + AI Practitioner · CCNA · PMP · Security+ · Network+ · Cloud+
Full bio and certificationsShow less
Nelson has spent fourteen years integrating and testing complex systems: the kind where hardware, software and networks from different vendors have to work together the first time, under real pressure.
At Strike Logix he owns networking and architecture: AWS design, hybrid networks, API connections, and moving small teams off manual checks and fragile spreadsheets. He maps how the work really happens before proposing anything, and every build ships with docs, a cost estimate and a decision record.
A degree in accounting means he reads a workflow the way an owner does: where the time goes, and what it costs.
At a glance
- Focus
- AWS architecture, hybrid networks, integrations
- Education
- M.S. Cybersecurity, completing Jan 2027 · B.S. Accounting
- Next exam
- AWS Advanced Networking – Specialty, Dec 2026
- Location
- Colorado Springs, CO
Certifications · each links to its Credly record
AWS Certified Solutions Architect – AssociateAmazon Web Services
AWS Certified AI PractitionerAmazon Web Services
AWS Certified Cloud PractitionerAmazon Web Services
CCNACisco
Project Management Professional (PMP)PMI
CompTIA Security+CompTIA
CompTIA Network+CompTIA
CompTIA Cloud+CompTIA
CompTIA A+CompTIA
Secure Cloud Professional (CSCP)CompTIA
Cloud Admin Professional (CCAP)CompTIA
Secure Infrastructure Specialist (CSIS)CompTIA
IT Operations Specialist (CIOS)CompTIA
Marc Whatley
Co-founder · DevOps, automation and security
Fourteen years in the U.S. Air Force coordinating fast-moving operations where the plan had to hold up under pressure. At Strike Logix he builds the pipelines that ship and run every tool, automates deployments and monitoring, and tests what we build the way an attacker would, so it's locked down before it goes live.
B.S. Criminal Justice · A.A.S. Information Systems Technology · AWS Solutions Architect Associate in progress
Full bioShow less
Marc spent fourteen years in the U.S. Air Force in fast-moving operations, where the plan had to work the first time and every step had to be checked before anyone moved.
At Strike Logix he owns the DevOps side: CI/CD pipelines, infrastructure as code, automated deployments and monitoring, and the AI features that sit on top of the systems Nelson designs. He also attacks our own builds before anyone else can, testing for the gaps an adversary would look for and closing them before launch.
A criminal justice degree gave him an investigator's habit: ask what could go wrong, follow the evidence, and write down what you find.
At a glance
- Focus
- CI/CD, automation, cloud security testing
- Education
- B.S. Criminal Justice · A.A.S. Information Systems Technology
- Next exam
- AWS Solutions Architect – Associate, Dec 2026
Contact
Tell us the task nobody wants to do.
A 30-minute walkthrough. You show us the workflow; we tell you plainly whether automation is worth it.