The Local Praxis site looks like a printed design manual. Archivo Black headlines. IBM Plex Mono everywhere else. A red accent you can count on one hand. No gradients, no drop shadows, no soft corners. That was deliberate.
Software marketing sites mostly look the same right now. Gradient hero. Serif-for-trust. Illustration of a friendly person using a laptop. A subtle drop shadow that suggests everything is slightly elevated, slightly floating, slightly soft. That look is not wrong. It is just what everyone uses because that is what the template said to do.
I do not sell software that came out of a template. It did not feel honest to market it on one.
What it references
The visual system pulls from a few specific places. None of them are web-native.
The grid and the type discipline come from Massimo Vignelli's Unimark work. His Piccolo Teatro posters. His New York subway signage from the late sixties. When you look at those, you are looking at a system that treats information as the object. Not a mood, not a vibe, not a brand. Information.
The banding and the horizontal rules come from the National Park Service Unigrid system. The same system you see on a trailhead sign at Padre Island. It is legible in harsh sun, to people who are tired and thirsty. It assumes the reader has something to do.
The type specimens come from Klim's Söhne page and from Linear's docs. Those two sites treat a monospace body as a first-class citizen, not as the font you put around a code block.
I am listing these references so they are attributable, not so the site borrows their authority. It does not.
What it signals
The site tells you a few things before it tells you anything else.
That I take the work seriously enough to think about how to present it. That I am more interested in a reader who notices than a reader who scrolls. That I am not optimizing for the lowest-common-denominator pitch, which means I am not optimizing for the lowest-common-denominator client.
It is honest advertising. The way the site looks is the way the software I build feels. Spare. Specific. Confident about what it is and what it is not.
Who it filters for
The site filters out buyers who want a rainbow-gradient, sticker-emoji, "revolutionize your workflow" kind of conversation. It filters in buyers who read menu boards and notice when the kerning is off.
That is the whole point. A Port Aransas charter captain looking to stop paying six percent on every booking is not going to care about the kerning. But on some level she is going to notice that the site is calm. That the page does not flash anything at her. That the numbers on the calculator add up in a way a platform's marketing page never would.
The kind of client I want to work with is not the majority of visitors. The site was never meant to convert everyone. It was meant to be unmistakable to the right people.
Why the restraint matches the work
When I build a custom booking system for a small business, I am not adding features. I am removing them. I am taking a stack that was built to serve ten thousand strangers and replacing it with software that was built to serve one business and do one thing better.
A good custom build is quieter than the SaaS it replaces. Fewer buttons. Fewer modals. Fewer third-party widgets whose privacy policies you have to read. It does the specific thing you actually need, and then it shuts up.
That is the product. The site is an honest advertisement for the product.
In closing
If this looks like a design book to you, and that is a good thing to you, we are going to get along.
If it looks cold or stiff or not fun enough, that is fair. I am not the right developer for your project. There are great developers out there who will make you something warmer and I am genuinely glad they exist.
The site is not trying to be liked. It is trying to be accurate.