Start with one problem.
Tell me which workflow costs your team the most time. We agree what the first 30 days should deliver, then I build it. Continue when the next piece is worth building.
Pause or cancel anytime. No minimum term, no lock-in.
75% refund in your first week if it's not a fit.
Your first 30 days
- Before you payA short call about one workflow. We agree a first milestone for the 30 days, and I tell you what will take longer.
- Week 1Access, a backlog in your priority order, and early work on staging for you to check.
- Weeks 2 to 4Weekly releases. Your team uses the tool on real work, and I fix what trips them up.
- Day 30We look at what shipped and decide together: continue, pause or stop.
The Safety Register for BMS took one cycle. On geomechanics.io, Packer Test Analysis took two weeks and the Coal Mine Roof Rating tool took two months. See the projects
Not every problem fits in 30 days. If yours won't, I'll tell you before you subscribe.
What's included
Your backlog, your priority
Submit as many requests as you want. Built one at a time, in your priority order. Plain words are fine, no technical specs needed.
Steady delivery
One focused build at a time, in your order. Larger projects split into weekly milestones.
Direct access
Work with your builder directly. No tickets, no account managers, no queues.
Revisions included
I refine until you're happy. No revision limits.
You own your code
The code I write for you is yours, in your repos. No per-seat licences, no lock-in.
Bug fixes included
If I built it, I fix it while you're subscribed. After you cancel, fixes resume when you resubscribe.
Pause anytime
Not enough work to fill a month? Pause your subscription and pick up where you left off. I credit unused days to your next invoice.
First-week exit
Not a fit after the first week? I refund 75%, no questions asked. I keep 25% to cover onboarding and work already delivered.
If I'm unavailable
Boxcut is one person. These safeguards keep your software running when I'm away.
Your code, your accounts
Code lives in your GitHub or GitLab. The app runs in your hosting accounts. Nothing depends on my login.
A handover document
Every project ships with one: how to deploy, where the data lives, how to restore a backup, and which services you pay for. Another developer can take over from it.
Backups in your account
Backup and recovery arrangements agreed for each project, in your own hosting account.
Holidays and sick days
I give two weeks' notice of holidays, and your cycle pauses for those days. If I'm ill, it pauses too. You don't pay for days I don't work.
Critical systems
The subscription has no out-of-hours cover. If a system needs a fast response at any hour, we agree a support plan for it first.
Pay for what you use
The 30-day cycle. Your subscription runs on a 30-day billing cycle, not a calendar month. The cycle starts the day you subscribe.
Pausing works like this. Let's say you subscribe and use the service for 20 days, then decide to pause. Billing stops that day, and you have 10 unused days. When you resume, whether that's next week or next year, I credit those 10 days to your next invoice.
The bottom line: You never lose paid time. If you pause, your unused days come back as a credit.
Billing runs through Stripe. You pay by card, and you cancel or update your card yourself in the Stripe billing portal. To pause, send me a message and I'll pause it the same day. Stripe holds your card details, and I apply the credit for unused days myself. Need an invoice or a purchase order? See procurement. Boxcut Studio on Stripe
Ready for software that fits the way you work?
I work with a small number of clients at a time. If I'm full when you enquire, I'll tell you the earliest date I can start.
Discuss a workflow