A custom app, built inside your own HubSpot or Monday tenant.
Some workflows have no app behind them, because the way your team works is specific to your team. We build that app where the work already happens, on the platform your team is signed in to all day.
It opens with a workflow audit, and the audit is complimentary.
What we mean by custom app development.
Most of these platforms have a name for it already, which is a private app. It is registered inside your own account, installed for your team alone, and it runs on the platform's own API and permission model.
That is a different object from a script on somebody's laptop, or a chain of automations that breaks the day a field is renamed. It has an owner, a place to look when it fails, and a way to be handed to somebody else.
We build on HubSpot, Monday.com, Slack, Atlassian, WordPress and Shopify, because that is where the working day already happens.
Where it runs
Hosting is decided in the audit, before anything is built. When the data cannot leave the building, the app runs on your infrastructure, under your own keys and your own logging.
How the work runs.
Four stages, and the first one is complimentary. Nothing is built until you have read what we propose to build and said yes to it.
Audit.
We sit with the people doing the work and follow one workflow from its trigger to the record it leaves behind. The write-up is yours to keep, whether or not you hire us.
Scope.
We write down what the app will do, which systems it touches, and what it will deliberately not do. You approve that document before anyone opens an editor.
Build.
We build inside your tenant, against the platform's own API, and we show you working software instead of a status report.
Hand over.
The code, the app registration and the runbook move to your side, and we walk one of your engineers through a deploy.
What you own at the end.
An app you cannot maintain without us is a dependency, not an asset. Everything below is handed over, and it is listed here so it can be checked off one item at a time.
- The source code, in a repository your team controls
- The app registration, inside your own account on the platform
- The credentials and secrets, issued and held by your team
- A runbook naming every system the app touches
- The audit write-up, whether or not we build anything
- The right to hand all of it to another developer
When we tell you not to build one.
Plenty of workflows are one app away from working, and that app is often already on the marketplace. When the audit finds one, we say so, and we point you at it. We would rather lose the build than sell you something you did not need, and the audit is complimentary either way.
Start with the audit.
Tell us which workflow costs your team the most time, and what it touches on the way through. Our CTO answers this one, and the first reply is a question rather than a proposal.
What happens next
- Our CTO reads what you send and writes back
- We ask about one workflow, not about everything you run
- The audit write-up is yours, whether or not we build