What custom web development covers
Custom work begins where your platform's settings and plugins run out. Requests tend to fall into four groups:
- Calculators and quote builders. A visitor enters measurements, quantities or options, gets a figure, and sends it to you as an inquiry. Our article on calculators and tools that bring in leads explains the case for them.
- Customer dashboards. A logged-in area where your clients see their orders, documents, invoices or project status.
- Booking and intake flows. Multi-step forms with rules: which services need a deposit, which slots are open, which questions depend on an earlier answer.
- Connections to other systems. Sending inquiries to your CRM, reading stock from your inventory software, or passing orders to accounting.
Proof: the tools we run ourselves
Two sites belong to us, and both depend on tools we wrote. FitnessVolt, our fitness publication, carries a library of calculators made for its readers. ShowMyIP publishes 113 free network tools in 12 categories, DNS and email checks among them.
We maintain those tools ourselves, so we plan for the dull parts of yours: quick loading, visitors who type the wrong thing, and updates to the platform underneath.
Our client work in this area is older. Between 2013 and 2018 we built Reinwork, a social network for real estate investors, as a custom application on the Laravel framework.
How we scope a custom feature
We scope one feature at a time, in writing, before anyone writes code. For each feature we record:
- Who uses it and what they are trying to finish.
- The inputs, the rules and the output. For a calculator that means the formula, with worked examples you have checked.
- Where the data goes afterward: an email, a database, another system.
- What the visitor sees when something fails, such as a missing field or a system that does not answer.
- How we both know it works: a list of test cases with the results you expect.
We can estimate a feature that has those five answers. We cannot estimate "a portal", so we ask questions until we have them.
The build happens on a copy of your site, away from the live one. You test each feature against your own examples, and it goes live after you sign off the test list. If you are in the city, we can walk through it together at our office on 8th Avenue.
What you must decide up front
Some decisions belong to you, and they cost less to make before the build than in the middle of it.
- The rules. Your pricing logic, eligibility rules or booking policy. We build the rule you state, so state all of it, exceptions included.
- The data. Where customer records live, who may see them, and how long you keep them.
- The other system. If we connect to your CRM or accounting software, check that your plan allows outside connections and name the person who can grant access.
- The owner after launch. Custom code needs someone to look after it. Agree who before the build: us, or your own developer.
When an existing plugin is enough
Much of what owners call custom already exists. The WordPress directory lists over 79,000 free plugins, and a search there for "appointment booking" returns hundreds of them, with more than a thousand for "calculator".
Use a plugin when your process matches the way the plugin works, or when you are willing to change your process to fit it. A mix is common too: the plugin handles the standard part, and we write the small piece that is yours.
Pay for custom work when your own rules drive the result: a quote that depends on your pricing tables, or a booking that depends on your crews and your stock.
We tell you which case you are in before we quote. If the whole site needs its own content structure, read about our custom CMS work. To talk about one feature, describe it in a few lines on the contact page.