MADTech / About
Built by the person you talk to.
Who you are working with
I started out as a software developer at New Well, working on the technical side of the business and learning the craft by shipping real things people depended on. From there I was hired by a marketing agency to build websites and software for their clients — which is where I learned what actually converts, and what happens when a build is treated as a deliverable instead of a business asset.
MADTech Solutions LLC is where I do that work for myself and for independent clients. It is a Michigan company serving the United States and remote worldwide. In practice it means one person who scopes, designs and builds the work, rather than a team that hands your project down a chain after the first call.
What I am strongest at is automating systems and processes — finding where a business is losing hours to repeated manual work and where small human errors are quietly costing money, then building something that removes both. Websites and web apps are usually the front door. That is the work underneath.
The honest limitation of working this way is capacity. I take on a limited number of projects at a time, which means timing genuinely matters — and occasionally the answer is that I cannot start when you need me to.
What I hold to
Everything is custom code
No templates, no page builders, no themes with your logo dropped in. That matters the moment you need something the tool does not support — a portal, a booking flow, a piece of logic specific to how your business actually runs. There is no ceiling to hit later.
You talk to the person building it
Nothing is relayed through an account manager and nothing gets handed to a junior once the pitch is over. The person who scopes your project is the person who writes the code. The trade-off is capacity — fewer projects at once, so timing matters.
Scope in writing, before anything starts
What is in, what is out, a price range built on your actual requirements, and a timeline I believe. If something would move that number, I say so at the time rather than at the invoice.
An honest no is part of the service
If a responsive site would do the job an app was going to do, or the real problem is the process rather than the tooling, you get told. Taking work I cannot do well costs us both more than turning it down does.
You own what gets built
Code, accounts and domains end up in your name, with a walkthrough of how to run it. No hostage situations, and no rented access to your own product.
The unglamorous states get designed too
Loading, empty, error, offline, half-finished. Most software feels cheap not because the happy path is ugly but because nobody thought about the other paths at all.
How a project runs
- 01
Send the messy version
A paragraph is enough. What it is, who it is for, and what is broken or missing today. I read it myself and reply — including an honest no if I am not the right fit.
- 02
Scope and a price range in writing
Before anything is built you get what is in scope, what is not, a range rather than a fantasy number, and a timeline. Nothing starts without that agreed.
- 03
Built in the open
You see it as it comes together, not at the end. Feedback lands while changing course is still cheap, which is the whole point of working this way.
- 04
Handed over properly
You get the code, the accounts in your name, and a walkthrough of how to run it. No hostage situations, no rented access to your own product.
The work behind this
What I have built so far, plainly:
- A paid website and video education platform for a business client — the full setup, front to back
- A church website, built and donated
- A SaaS product of my own
- Websites and software for agency clients, which I cannot discuss in detail
- A church management system currently in build, to be sold as a product
The project scenes on the homepage are illustrative rather than captures of that work. I would rather tell you that outright than imply a portfolio I have not published yet. Ask and I will walk you through the real thing — including this site, which I designed and built.
Bring the messy version.
Tell me what you are trying to build and you get a straight answer on scope, cost and timeline — or an honest no.