BUILD
The part of the website that has to actually work.
Templates, functionality, integrations and the code holding it together. Written so the next developer can read it, and so it keeps running after we’ve gone.
Plenty of what we do starts with somebody else’s code, no documentation and a developer who’s stopped replying. That’s ordinary work for us, and we’ll tell you honestly whether it’s worth keeping.
What we build.
What we build.
Front-end work
Clean HTML, CSS a person can maintain, and JavaScript that fails gracefully.
Back-end and application work
PHP, MySQL, background jobs, permissions, admin screens. The parts nobody sees until they break.
Custom functionality
Calculators, configurators, portals, booking, quoting, member areas and internal tools.
Integrations
CRMs, ERPs, payment providers, shipping, email platforms, accounting, scheduling.
APIs, both directions
Using somebody else’s, or building one so another system can talk to yours.
Taking over unfinished work
We read what’s there, tell you what it’s worth, then finish it or replace it.
- PHP 8
- JavaScript
- MySQL / MariaDB
- HTML
- CSS
- WordPress
- WooCommerce
- Drupal
- REST APIs
- Webhooks
- Composer
- Git
- Apache
- Nginx
- Cron
- Redis
How we build.
The expensive problems usually aren’t code problems
They’re decisions nobody wrote down. A field that means two different things depending on who filled it in. An integration nobody owns. A plugin doing something critical that everyone’s forgotten about.
The right amount of custom
Custom code is a liability as well as an asset. Every line is something to maintain, secure and eventually upgrade. We use the platform where it’s good, use a well-maintained package where one exists, and write custom code where the requirement is genuinely yours.
What to expect
- We work out the requirement, not just the request
- We read what already exists
- We pick proven technology on purpose
Small, well-defined work is billed hourly. Anything larger gets a written scope and a price.
Development questions.
Development questions.
Can you take over a project somebody else started?
Often, yes. We’ll ask for repository access, hosting access and whatever documentation exists, then spend a set amount of time reading before quoting.
Do you work with our in-house developer?
Regularly. Sometimes as extra capacity, sometimes for an area they don’t cover, sometimes as a second opinion. We work to your conventions and your branch strategy.
Will we own the code?
Yes, on work billed as a project: your repository, your hosting, your code, once it is paid for. The Website Design monthly plan works differently, and says so on its own page: the website is released after 12 monthly payments.
Functionality that doesn't exist off the shelf.
DrupalWhere structured content and editorial permissions matter.
Our WorkClient sites you can open, including a custom PHP rebuild.
Functionality that doesn't exist off the shelf.
DrupalWhere structured content and editorial permissions matter.
Our WorkClient sites you can open, including a custom PHP rebuild.
Development is scoped and quoted. We look at what you have before we put a number on it.
Not what you need? See all three ways we work
Not what you need? See all three ways we work
Something that needs building properly?
Describe what it has to do, and what it currently takes to do by hand. We’ll tell you what’s involved.
Rather talk it through? Call 833-336-6453.