Making a Mark with AI
Making a Mark with AI
It depends on what we build together — and that's intentional. Some clients take full ownership once it's delivered, the code is theirs, free and clear. Others prefer we stay on to support and evolve it. Either way, we shape it around what works best for you.
It stays yours and stays private. It's never sold, and never used outside of building and supporting your own system.
If it has an API or an export, we connect to it.
Your call. Keep Making a Mark on board for support and changes, or take it over and own it outright - either way, it's yours.
If an existing tool fits the workflow, that's the better answer. Custom makes sense when your process crosses several systems, depends on rules specific to your business, or forces your team into repeated manual work standard tools don't handle. Part of the first conversation is deciding whether a custom build is even justified.
Usually not. Most projects sit around the tools you already use — pulling information together or automating the work between them. If replacing something is the better route, that becomes an explicit decision, not a surprise mid-build.
We start with the recurring problem that costs the most time or creates the most risk. The first build should be small enough to prove useful quickly and clear enough to measure.
Then we'll say so. Sometimes the fix is a process change, a feature in a tool you already own, or a simple automation. The consultation is about finding the right next step, not forcing every problem into a build.
Every project is priced on its own, based on what we're building. You'll know the full number before anything starts - no surprises.
It depends on the project, but you'll have a concrete plan within 3 business days of us kicking off.
Depends on the project. We'll tell you exactly what we need up front - usually some access, your data, and a little of your time. And if you'd rather hand us the legwork entirely, we can take that on as part of the engagement.