The Crutch
It started with a printer my partner bought on a whim.
Anisa brought home a Bambu Lab A1. Cheap. Not a tool (yet). But rather a toy, something to fill a weekend. We printed the usual nonsense. Fidgets. Pokemon figurines. Things nobody needed.
But something opened up. For the first time I could think of an object and hold it two hours later. That gap between idea and thing had always been someone else's to close. Now it was mine.
So I went looking for a problem I was actually equipped to solve.
The problem was already there
An endurance athlete trains for a year to have one day.
They wake at four for months. They ride in the rain. They lose weekends, skip dinners, plan a whole life around a single date on a calendar. Then the day comes, and it hurts exactly as much as they knew it would, and they cross the line.
And then they go home with nothing.
A medal in a drawer. A finisher's shirt they'll wear twice. And a file on a server, a GPS trace, a line on a screen, the entire year rendered as data that will never be looked at again.
That was the gap. Enormous effort, nothing left behind. I knew it because I'd lived it, and everyone I rode with had lived it too.
So I made the thing that should have existed. Real terrain, from real elevation data, built from the route itself. Something with weight. Something that goes on a wall and stays there.
Reinforcement, and a deadline
People loved it immediately.
Not politely. Not the way friends tell you your idea is nice. They wanted them. They sent me their routes unprompted. That kind of signal is rare, and when you get it, you push.
There was also a deadline. We had a newborn coming.
Every business I'd built before was conventional, the kind that puts you in a truck, in a room, on a site, out of the house. This time I needed something different. Something that lived at home, where I was going to need to be.
That constraint turned out to be a gift. It ruled out every version of this business that didn't scale from a desk.
The part I'd rather not admit
I couldn't build my own models.
I didn't know Blender. I didn't know how to pull DEM data. I tried, repeatedly, at the beginning, and got nowhere worth showing anyone.
So I used Map2Model. It let me turn an idea into something printable and sellable in an afternoon, and that speed is the only reason Type II exists. It proved the business was viable before I had any right to know that.
But I knew what it was. It was a crutch. And a crutch you build a company on is an Achilles heel.
Every order I took ran through a tool I didn't own, couldn't change, and couldn't guarantee would exist next year. There were only two ways out. Partner exclusively with the owner. Or build my own.
What I saw in the market
There are a lot of map tools out there.
Most are bad. A few are genuinely good. But even the good ones optimize for features over experience. Every capability exposed, nothing curated, and no opinion about what you're actually trying to make.
More importantly, almost all of them are built for hobbyists. For fun. You can tell by what they're proud of: tiling gimmicks, puzzle pieces, novelty. They're built for hikers who want their trails on a shelf.
I wasn't building for hikers.
I was building for cyclists and marathon runners. People who understand pain and suffering as a discipline. People who know exactly what Type II fun means, because they chose it on purpose and will choose it again.
That's a market I belong to. I know what they value, what they've sacrificed, and what they earn. Which means it's my price to set.
The north star
So the brief became simple.
Build the most efficient tool in existence for creating reliable, high-quality map artifacts - fast, and built to sell. On a platform that's clean and worth looking at.
Not a toy. A business instrument. Something a creator can put revenue through.
That single sentence has governed every decision since. Every feature gets scrutinized and tested until it's bulletproof, not "working," not "fine," bulletproof before I'm allowed to start the next one. It's slower. It's the only reason any of it holds.
Why size, not colour
Everyone else competes on colour.
I compete on scale.
I don't just want clean, accurate output. I want it to hold up at any size — an 8.5×11 on a desk, and the same file scaled to a ten-foot wall if the job calls for it. Small pieces are a product. Large-format is a different business entirely, and almost nobody can do it, because it breaks every browser-based tool the moment you ask.
That ceiling is the advantage. It's the thing that took the most engineering, and it's the thing I'd defend last.
Why I'm publishing this
I have no coding background. None.
This is the most complex thing I have ever attempted, and I'm proud of where it's gotten to. It also would have been impossible eighteen months ago, for someone like me.
So I'm going to write all of it down. The architecture decisions. The features. The bugs that cost me entire nights and taught me something permanent. The outages. What I got wrong and how long it took to notice.
Not a highlight reel. The actual log.
Because there are people out there with an idea and no idea how to build it, who assume that's the end of the sentence. It isn't. It was for a long time. It isn't anymore.
This is how it actually went.
