Custom Applications

Member portals with real-time availability and booking, commerce and subscription platforms, event registration systems with linked parent and player accounts, patient intake flows, a web-based product design tool, internal dashboards and custom reporting, and backend APIs that aggregate data from several outside sources.

Yes, and a good deal of our application work does. For Organize My Drawer we built a browser-based design tool that converts a customer's drawer layout into cut files for the laser cutters on their factory floor, along with the back-office workflows the factory runs on. The website is the entry point, not the system.

Yes. For Pathlight Mood & Anxiety Center we built a custom application that pulls events from Fonteva, generates the registration forms around them, and signs attendees up in Salesforce. Their intake forms also create and manage contacts in both Salesforce and HubSpot. We have run scheduled syncs against client databases and HR directories, and integrated with existing authentication systems.

Yes. We have built commerce-enabled event registration with Authorize.Net payments, a configurator that prices a custom-manufactured product from the customer's own specification and takes payment for it, and a membership platform running subscription plans of different lengths alongside individual purchases and physical product sales, with receipts and order emails handled automatically. Where it suits the project we build on Drupal Commerce; where it does not, we build the commerce logic directly into the application.

Yes, and we do this often. We review the existing codebase, hosting and data model first, tell you honestly what is worth keeping, and then extend and maintain it. We have looked after client applications for years that were built before we were involved.

Drupal and WordPress where a CMS belongs underneath, PHP and MySQL, React and modern JavaScript on the front end, Ruby on Rails where that fits, and modern frameworks such as Astro and Payload. We choose based on the problem, the systems you already run, and who will maintain it afterwards.

Yes. We build APIs for use by mobile applications, partner systems and internal services, and we consume third-party APIs the same way. For one client we built an autonomous backend API that pulls project reports in from a variety of different sources.

Yes, and this is where most of the real cost of an application sits. We offer retainer and as-needed plans covering dependency and security updates, integration monitoring, alerts when a scheduled sync fails, bug fixes and ongoing feature development.

You do. Every piece of code and design is yours, documented and structured so your own team or another vendor could pick it up. You paid for it, you own it.

However suits you. We work in whatever your team already uses, whether that is Slack, Teams, email, or a project tool like Monday, Wrike, Teamwork or Asana. For some clients we are effectively the web team: their editors and staff come to us directly with requests rather than routing everything through one point of contact, and we take in, prioritize and run that work ourselves. For others a single contact is simpler. Either way the developer doing your work is the one managing it, so there is no account layer between you and the person writing your code, and none to pay for. We fit how you already work rather than asking you to adopt our process.