Documents into systems
Invoices, forms, applications, supplier paperwork. Anything that arrives as a document and gets retyped into software by a person.
Removes: every manual re-key, and the errors that come with them.
BUILD TIME: 2 TO 3 WEEKS
Describe the process.I’ll build the machine.
Nightshift builds automations and software for small firms. Fixed price, agreed before anything starts. You see it working on your own data before you pay the balance. No proposals, no day rates, no account manager.
NS
Describe a process your team does by hand. I’ll ask a few questions, then give you a rough scope and the size of job it is. If it’s a bad candidate for automation, I’ll say so.
This page is running the same thing I’d build for you.
Stored: your messages, and your email if you leave one. Used to write your reply. Nothing else, no tracking.
Three sizes of work. Small jobs are a few days. Automations remove a process your team is doing by hand. Builds create something that doesn't exist yet. All fixed price, agreed before anything starts.
Build times below are what these actually take. Savings depend entirely on your volumes, so I won't publish an average that means nothing. The chat above works yours out from your own numbers.
SMALL JOBS · FIXED PRICE · 1 TO 7 DAYS
Not everything needs a four-week build. One report that should generate itself. A spreadsheet two people are keeping in sync by hand. A form that should be writing into your system instead of your inbox. One integration that never got finished. If it's a few days of work, it's £1,000 to £3,500, invoiced once, and you'll usually have it inside a fortnight.
If it turns out to be bigger than that once I've looked at it, I'll tell you before starting, not halfway through.
AUTOMATIONS · FIXED PRICE · 2 TO 4 WEEKS
Enquiry handling
New enquiries get researched, qualified, routed to the right person and answered, in minutes rather than days.
Removes: leads sitting unread, and the follow-up nobody remembers to send.
BUILD TIME: 2 TO 3 WEEKS
Quotes and proposals
Notes, pricing rules and approved wording assembled into a first-draft quote. A person still checks it before it goes.
Removes: the two hours a quote takes to write from scratch.
BUILD TIME: 2 TO 4 WEEKS
Client onboarding
Signed client triggers the whole sequence. Data collection, checks, system setup, welcome email, internal handover.
Removes: the half day of admin every new client costs you.
BUILD TIME: 3 TO 4 WEEKS
Getting paid
Overdue invoices found, reminders staged and sent, the account owner told before it gets awkward, escalation when it needs it.
Removes: chasing that only happens when someone remembers.
BUILD TIME: 2 WEEKS
Reporting packs
Numbers pulled from your systems and spreadsheets into the same report every week or month, with the exceptions flagged at the top.
Removes: the day a month somebody loses to copy and paste.
BUILD TIME: 2 TO 3 WEEKS
Joining up your systems
Your CRM doesn't talk to your accounts package. Your job software doesn't talk to either. This is the plumbing between them.
Removes: double entry, and the arguments about which system is right.
BUILD TIME: 2 TO 4 WEEKS
Compliance evidence
File reviews, audit trails, submission packs, the paperwork that proves you did it properly. Assembled and checked, ready for a human to sign off.
Removes: the scramble before a deadline or an audit.
BUILD TIME: 3 TO 4 WEEKS
Deadlines and renewals
Filing dates, renewal dates, annual reviews. Who owes you what, chased automatically until it arrives, escalated when it doesn't.
Removes: the week before every deadline spent asking clients for the same things.
BUILD TIME: 2 TO 3 WEEKS
BUILDS · FIXED PRICE PER PHASE · 6 WEEKS AND UP
Internal tools
The thing your team currently runs on a shared spreadsheet that four people edit at once. Made properly, with permissions and a history.
BUILD TIME: 4 TO 8 WEEKS
Client portals
Somewhere your clients log in, see their own information, upload what you need and stop emailing you for updates.
BUILD TIME: 6 TO 10 WEEKS
MVP, first version
You have a product idea and need a real, working first version in front of users. Not a prototype. Something people can actually use.
BUILD TIME: 8 TO 12 WEEKS
SaaS platforms
Multi-tenant products with accounts, billing, permissions and integrations. Built to be run and sold, not demoed.
BUILD TIME: 12 WEEKS AND UP, PHASED
Integrations
Payments, banking, HMRC, CRM, whatever API you need to be talking to. Including the awkward regulated ones.
BUILD TIME: 2 TO 6 WEEKS
Mobile apps
iOS and Android, built and shipped to the stores.
BUILD TIME: 8 TO 12 WEEKS
One example, start to finish, so you know what you’d be buying. This is the shape of a typical automation, not a specific client.
NOW
A firm of twelve. Two admin staff spend most of Monday taking job sheets out of email, keying them into the CRM, then keying the same details into Xero to raise the invoice. Around forty jobs a week. Every few weeks one gets missed entirely and only surfaces when a client queries a bill. Nobody knows how many, because nobody’s counting.
AFTER
Job sheets are read as they arrive. The CRM record and the draft invoice are both created. Anything that doesn’t match a known client, a known rate or a known job number is held in a queue for a person to look at, rather than guessed at. One person spends twenty minutes a week clearing that queue. Nothing gets missed silently, because the queue is the record.
WEEK 1
I map the actual process, not the one in the manual. I read fifty of your real job sheets, including the messy ones.
WEEK 2
Build. You get access to a working version on your own data at the end of the week, running alongside the manual process.
WEEK 3
You use both in parallel and we compare. Anything it gets wrong, I fix. The exception rules get tuned to your business.
WEEK 4
It runs on its own. I’m on hand for thirty days after.
Notice what isn’t in there. No discovery workshop, no requirements document, no steering call. I read your actual paperwork and build against it, because that’s faster and it’s the only way to find out what your process really does.
"It won't work on our messy data."
It's always messy. That's why nothing off the shelf has fixed this already. The build assumes mess and holds back anything it isn't sure about, rather than guessing and creating a different problem.
"We'll be locked in to you."
You own the code and the accounts it runs on. It's written in normal tools any developer can pick up. If you never speak to me again it keeps running.
"What if it breaks in six months?"
Thirty days of fixes included after go-live. After that it's an hourly rate if you want me, and no obligation if you don't. There's no retainer and I won't try to sell you one.
"We've been burned by an agency before."
Fixed price agreed before anything starts. Half up front, half when it does the job. If the demo doesn't do what the scope says, you don't pay the balance.
"How do we know it's worth it?"
The chat at the top works it out from your own numbers. If the maths doesn't work, it will tell you so. I'd rather lose the job than build something that pays back in four years.
01
The conversation
TODAYTen minutes in the chat above. You get a rough scope and the size of job it is. Free, no obligation, no follow-up calls you didn’t ask for.
02
The written scope
+2 WORKING DAYSI check the scope myself and send it with a fixed price. One page. You say yes or no. No meetings required.
03
The build
+2 TO 4 WEEKSHalf up front. You get a working demo on your own data, not slides. Pay the balance when it does the job.
WORK STARTS AT £1,000.
Small jobs are £1,000 to £3,500 and take one to seven days, invoiced once, in full, before I start. Automations are £5,000 to £8,000 over two to four weeks, half up front and half when the demo does the job. New software is quoted per phase from £15,000.
That's the whole number in every case. No retainer, no day rate, no surprise invoice in month three. Running costs are yours and named before we start, usually under £100 a month. If your process isn't worth what it would cost to fix, the chat above will tell you so.
Scott O’Sullivan
Fourteen years selling into regulated financial services. Then I learned to build, properly. Now I ship production software, including the intake you just used and everything behind it.
You deal with me from the first message to the last deployment. I scope it, I’m accountable for it, and I write most of it. On larger builds I bring in developers I’ve worked with before, so the size of the job isn’t the constraint. What you won’t get is an account manager, a discovery workshop, or a different person turning up to deliver than the one who sold it.
MANCHESTER. WORKING ACROSS THE UK.