Developers on demand
When standard software will not bend — a report that does not exist, a process that is yours alone, a legacy database that has to come across — you book time with the same team that writes the product. In blocks of days, priced before you commit.
Day rates, all in
USD85 per day
Engineer
USD150 per day
Project manager
Blocks start at five days. Your engineer starts within 48 hours of payment, and unused days roll over for 90 days.
Not sure what you need yet? Book a call and we will scope it with you.
Written by this team
These kinds of work make up almost everything we are asked for. If yours is not on this list, describe it anyway — the assessment is free either way.
Each of these started as a sentence in an email. Every screen below is in a product you can open today.
A module that did not exist
Savings and loans were running, but nobody could see the cash position across branches without a spreadsheet. We built the treasury module — positions, transfers between branches, and the daily reconciliation — inside the same system, so the numbers come from the ledger rather than from a copy of it.
A process that was ours alone
Standard scheduling software books a room for an hour. A theatre list books a surgeon, an anaesthetist, a table, a set of instruments that has to come back from sterile supply, and a patient who has to be starved from a particular time. We built the list the way the theatre runs it, and the rest of the hospital reads from the same record.
A document somebody actually needed
A school's fee ledger is correct and unreadable — that is why the bursar's office spends the first week of term explaining it. We rebuilt the statement so a parent sees what was charged, what was paid, what a bursary covered and what is left, on one page, in the school's own layout.
BridgeERP is not software we resell. The apps in the products above — the ledger, the fee run, the theatre list, the treasury desk — were written by the same engineers you book here.
That is the whole difference. Someone who has to learn your system first will spend your first days reading it. We already know where the code is.
Your engineer has already worked inside the modules yours will sit next to, so the first day is spent building rather than reading.
We write to the same standards as the product, so the next person who opens it — us or anyone else — can read it.
Custom work that ignores the platform breaks at the next release. Ours is built to survive one.
This is a ten-day block, which is the size most jobs land on. A five-day block runs the same way with weeks one and two folded together; longer blocks repeat weeks two and three until the work is done.
Before you pay
Describe what you need in your own words and attach whatever you already have — a screenshot with arrows on it, a spreadsheet, an email thread. We read it, work out what it will take, and reply with a technical answer and a price.
Free. No commitment. No account needed.
Week one
We agree exactly what is in the block and what is not, and write it down. Your staging copy goes up the same week. By the end of it there is something on screen to react to.
You confirm the scope note.
Week two
The work goes onto staging as it is written, not at the end. You open it, tell us what is wrong, and we change it while the engineer is still on the job.
You look at staging and comment.
End of week two
Tested against your own data, not sample data. When you accept it, it goes to your live system at a time you have agreed — outside working hours if that is what it takes.
You sign it off before it goes live.
After
You get the code, a written note of what was built and why, and a named person to come back to. If you book again, the same engineer picks it up.
Yours to keep — see what you own, below.
Every day in a block is a working day, and every day ends with a written progress note. Days you do not use roll over for 90 days.
Two roles, booked by the day. Most jobs need only the first.
A full-stack developer who writes, tests and ships the work.
USD85per day
An engineer talks to whoever you nominate. If you would rather not run the job yourself, add a project manager.
Runs the block so you do not have to — scope, sequencing, and the conversation with your team.
USD150per day
On a managed block, most of the booked time is still engineering. Your scope note states the split before you pay.
Working time
A full working day of hands-on build, not a fraction of one billed at a rate.
Review and testing
Code review and tests are inside the day, not an extra line.
A written note
Every day ends with what was done, what is next and anything blocking it.
Your environments
Staging is set up and maintained for the length of the block at no extra charge.
Pick a role and a block size. The total below is the total — it is priced by the same system that issues your invoice, so the number here and the number at checkout are the same number.
Booked in blocks from 5 days. Unused days roll over for 90 days.
These are terms, not promises. They are the same ones on your order.
Everything written for you is yours: the source, the documentation and the right to take it anywhere. We do not licence it back to you and we do not hold it.
Blocks start at five days. Anything you have not used rolls over for 90 days, so a block that finishes early is not a block you have wasted.
From payment, not from enquiry. If we cannot start in that window we will tell you before you pay, not after.
Work is built on a staging copy of your own system. You look at it and accept it before it is released, and the release happens at a time you have agreed.
You see the total before you pay, the invoice comes by email, and you settle it from your portal. There is no separate charge for review, testing or the staging environment.
A block is a block. When it ends it ends, and there is nothing to cancel.
We will tell you what it takes. That part is free.
You do not need a specification. Describe the problem in your own words and attach whatever you already have — a screenshot with arrows drawn on it, a spreadsheet, the email thread where somebody explained it better than you can.
We come back within two working days.
No brief and no time to write one? Book a call and we will write it with you.
Four things are required. Everything else helps us answer faster.
You pay for the block up front. The total you see when you pick the days is the total: review, testing and the staging environment are inside it. The invoice arrives by email and you settle it from your portal. If a job turns out to need fewer days than you booked, the unused days roll over for 90 days rather than being refunded.
We tell you as soon as we know, not at the end. You decide whether to add days or to stop where you are and take what is built. We do not carry on and invoice you for the difference.
You do — the source, the documentation and the right to take it to anyone else. There is no licence back to us.
Custom work that fights the platform breaks at the next release. We write to the same standards as the product itself, and anything we build for you is tested against the version you are on before it is released.
Yes. Your team gets access to the same staging environment and the same code, and the daily note goes to whoever you nominate.
Then the job is usually an implementation rather than a development block. Start with a Success Pack — it covers configuration, migrating your data and training your people — and come back here when something needs building that does not exist yet.
See Success Packs →Yes. Tell us what you need looked after and we will quote it. It is not automatically included in a block, and we will not add it to your invoice without asking.
Send us the job →Book the days if you know what you need. Send us the job if you do not — either way you will have a price before you commit to anything.
