How a project runs.
You should know what you are buying, how you will see progress, and what you will have at the end. Here is the whole process, the same for a content batch, a workflow, a release, or a handoff.
A call about the problem.
Thirty minutes with our team. You describe what is slowing you down or what you need to build. We ask questions, tell you whether we are the right fit, and suggest a first step. No preparation needed.
A written scope and a fixed price.
Deliverables, what is excluded, what we need from you, milestones, acceptance criteria, and the price. Short enough to read in one sitting. If the problem needs investigation first, we propose a short paid discovery with its own deliverables instead.
We design it and propose it.
We sit down with you, map the work, and propose a design: screens and data, workflow and permissions, posts and captions, or a lesson plan. You review it before anything is built.
Build in the open.
Progress shows up as working software, a live workflow, or draft posts at scheduled reviews, usually weekly. If a new requirement appears, we tell you what it changes in scope and cost before we build it.
Test against what we agreed.
Automated tests for the behaviour that matters. The three inquiry scenarios. Your approval round on the content. Known limitations are written down, not discovered later.
Hand over, then decide what is next.
Files, source code, documentation, deployment, and a walkthrough for your team. You own the result. Monthly support or the next phase is agreed separately, never assumed.
Working with us
What we need from you
Someone who can make decisions. Access to the systems and people involved. Honest feedback at reviews. We are clear about what we are waiting on, and we ask the same.
What you can expect from us
A named person responsible for your project. A scope you can hold us to. Plain talk about risks and trade-offs. Working results at every review.
Who does the work
A team of experienced engineers, designers, producers, and trainers. Our people have engineered and tested software where mistakes are expensive, co-founded a technology school that taught about a thousand engineers, and build and run products of our own. Much of our code is implemented by AI coding agents working inside architecture rules, structure checks, and test gates our senior engineers set and review. It is the same discipline we recommend to clients who want to use AI: a clear job, firm limits, and someone checking the output.
Bring the problem as it is. We will tell you what we would do first.
30 minutes with our team · Free, and useful either way