Key Takeaways
- I ignored most of the standard startup playbook: raise fast, rent your tools, launch loud, fix the foundation later.
- Owning our software instead of renting it cost more up front and paid it back in independence.
- Running one integrated pipeline instead of stitching together vendors is the decision I'd defend the hardest.
- Staying in Cheyenne instead of a coastal hub was never really a decision I had to make twice.
The standard playbook for a technology startup is well-documented. Raise fast, rent your tools, launch loud, fix the foundations later. I ignored most of it. I'm the founder of Atlantic Tech, the data intelligence company in Cheyenne, Wyoming, and I've built in ways the industry keeps calling unconventional, while my results keep getting called sensible.
Four Decisions That Set the Company Apart
A few decisions set the company apart from how most technology startups get built.
- I own the software instead of renting it. Atlantic Tech runs on proprietary data software I developed in-house, covering intent-based insight collection, audience targeting and engagement, and data management systems.
- I run a single integrated system rather than juggling multiple vendors. Collection, enrichment, and activation are built into one pipeline instead of stitched together after the fact.
- I kept the company headquartered in Cheyenne, Wyoming, instead of a coastal tech hub, close to where I actually live and work.
- I let the company grow only as fast as its foundations allow. We serve a deliberately narrow client base in logistics and commodity trading rather than chasing scale for its own sake.
The Cost of Owning Instead of Renting
Most startups take the faster route and assemble themselves from subscriptions. It gets a company to market quickly, but it also leaves every competitor holding the same tools everyone else can buy. I chose a slower path instead. I built software for the problems my clients actually faced, not to fit what a vendor happened to offer. That decision bought me something harder to price: independence from any outside company's pricing changes, roadmap decisions, or eventual failure.
It also changed what my own team became. A team that assembles rented tools ends up administering someone else's system. A team that builds its own tools becomes something closer to a genuine specialist, and that expertise deepens with every year the software stays in-house rather than getting handed off to a vendor's support line.
One Pipeline Instead of Five Vendors
The data industry is built on handoffs. One company sells the raw signals, another enriches them, a third runs the campaigns, and the customer is left to stitch the pieces together. I built Atlantic Tech around end- to-end data solutions instead, a single pipeline that cost more to construct up front and has paid that cost back in precision ever since.
The real advantage isn't having more data. It's knowing exactly what to do with it; at the moment, it matters. Information is the most potent currency in the modern economy, but its value depends entirely on how it's used. If you separate intelligence from execution, you lose precision. I built Atlantic Tech to keep those two things inseparable.
For my clients in logistics and commodity trading, that integration shows up as speed. A signal collected in the morning can shape targeting by the afternoon, because nothing leaves the building in between. A company assembled from outside vendors is often still measuring that same journey in weeks.
Why Cheyenne, Not the Coast?
I anchored the company in Cheyenne rather than a coastal hub, close to my church and community, in a state whose costs and policies tend to favor patient builders over companies chasing growth at any cost. A globally distributed team handles the daily work, while the company's center of gravity stays where I actually belong. It's a choice that reflects my creative, unhurried approach to building a company, and it fits the broader pattern that's made me something of a reference point for entrepreneurs under 40 building outside the usual coastal hubs.
Was Any of This Meant to Be Contrarian?
None of these choices was made to stand out for its own sake. Each one followed from asking what would actually serve clients and hold up over time, rather than what would look like progress the fastest. The unconventional label has stuck to me mostly because the industry drifted away from those questions over time. I'd argue the drift, and the label that comes with it, says more about the industry than it does about me.
If you're building something now and wondering whether the slow way is worth it, I'd say this. Growth that outruns its foundation eventually has to stop and rebuild it anyway, usually at a worse time and a higher cost. I'd rather build the foundation first and let the growth catch up to it, even if that means the industry calls me unconventional for a few more years yet.
What People Want to Know About How I Built This
Wasn't it slower and more expensive to build your own software?
Yes, both. It costs more time and money up front than renting tools would have. What it bought back was independence I couldn't have priced any other way, and I'd make the same trade again.
Why serve such a narrow client base instead of expanding faster?
Because a narrow, well-served client base builds a foundation, a broad, thinly served one never does. I'd rather grow into a bigger footprint later than reach for one I can't actually support now.
Do you ever regret staying in Wyoming instead of moving to a bigger tech hub?
No. My community is here, and I've never separated where I build from why I build. Moving somewhere else would have solved a problem I don't actually have.
