MADTech / Quincy, MI

Websites, apps & software for your business.

I design and build custom websites, mobile apps, SaaS products, business software and automation for companies, entrepreneurs, nonprofits and teams within 75 miles of Quincy, Michigan. From Coldwater and Battle Creek to Kalamazoo and Fort Wayne, you work directly with the developer building your project.
Request a quote

Where I work

My local service area covers a 75-mile radius around Quincy, Michigan, including Quincy, Coldwater, Bronson, Union City, Sherwood and the communities between them. That is a straight-line radius; driving distances will vary. The cities below are examples, not a limit on which communities I serve within that area.

Michigan: Battle Creek, Kalamazoo, Portage, Marshall, Hillsdale, Jackson, Sturgis, Three Rivers, Albion, Adrian, Charlotte, Lansing, East Lansing, Ann Arbor.

Indiana: Fort Wayne, Angola, Auburn, Kendallville, Goshen, Elkhart, Mishawaka, South Bend.

Ohio: Bryan, Defiance, Wauseon, Toledo.

Most collaboration can happen remotely. If meeting in person would help, we can discuss it when we scope the project. Beyond this local area, I also work remotely across the United States and worldwide.

Why hire someone here

Work directly with the developer

You describe the problem to the person designing and building the solution. We can review the work remotely and discuss whether meeting in person would help when we scope the project.

I know what small-market business looks like

A small business in Branch County may not have a marketing department or an IT person. The thing I build has to be usable by whoever happens to be at the counter, on a phone, with one hand free. That constraint shapes the whole build.

Same standard, local or not

The process stays the same wherever you are in the service area: custom code, scope in writing before anything starts, and code and accounts in your name at handover. You do not need to travel for routine project reviews.

Web design, apps, custom software and automation

What to bring to the first conversation

Tell me what your organization does, who needs to use the finished build, and what they should be able to do with it. For a website, start with the action a visitor should take. For an app or software product, describe the main task. For automation, walk through one job you currently repeat by hand.

Include the tools you need to keep, any deadline you are working toward, and where you are in the service area. We can scope and review the work remotely; if an in-person conversation would help, mention that too. You do not need technical requirements or a finished specification to make an inquiry.

How I work

Priced per project, never by the hour

Every project is different, so every price is worked out from your actual requirements rather than read off a list. You get a figure in writing before anything starts, and you are buying a finished thing rather than my time.

Custom code, not drag-and-drop

I do not build on page builders or theme editors. If you already run a platform that allows real custom code — GoHighLevel, for instance — I can build inside it. What I will not do is assemble something from blocks and call it bespoke.

Fast is possible, and it is priced as fast

Tight deadlines are often doable — a website in a few weeks is realistic. Compressing a schedule costs more, and how much depends on the size of the build. I will tell you what is achievable before you commit to a date.

Building only, not marketing

I design and build. I do not run ads, SEO or marketing campaigns, and I would rather say so than take money for something outside what I do well.

How a project runs

  1. 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.

  2. 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.

  3. 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.

  4. 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.

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. It reaches me directly, not a queue.