AscendryxServices
Build it, host it, keep it running
We are not a project shop that disappears at handover. The system we build is a system we then operate, which changes how we build it in the first place.
Engagements
Four ways this usually starts
Custom build
You have a process that no product matches. We map how the work actually happens, including the shortcuts people take, then build a system around that rather than around an ideal version of it.
- Discovery written up as a scope you can read and argue with
- Fixed quote before development starts
- Built in stages you can see working
White-label deployment
One of our products, running under your brand and your domain, with your own tenant and data. Faster and cheaper than a custom build, because the hard parts are already solved and already tested.
- Your name, logo, colours and domain
- Your data separated from every other client
- Configuration and training included in setup
Hosting and support
Servers, backups, monitoring, updates and the phone call when something is wrong. Monthly, with a defined response time and no surprise invoices for ordinary maintenance.
- Nightly backups held off the main machine
- Automatic restart and alerting when a service stops
- Security patching as part of the retainer
Integration work
Connecting what you run to what you use: payment gateways, SMS, email delivery, document storage, or another vendor's system through their API.
- Payments, including local wallets and QR
- SMS and transactional email
- API keys and signed links for machine to machine access
Process
How a project runs
No long discovery phase billed by the hour. We would rather get something in front of your staff early and correct it than write a beautiful document nobody reads.
Brief
A call, then a written scope: what the system must do, what it will not do in version one, what it costs and who owns what. Nothing is built until you have signed that.
Build
Work lands in stages. You get a link to a working version early and keep getting updates, so corrections happen while they are cheap.
Go live
Data migration, staff training and a supervised first week. We watch the system closely while your team learns it and fix what the real world surfaces.
Run
Monthly hosting and support. Your system keeps getting the fixes and improvements we make across the platform, not just the ones you pay for.
Straight answers
What we will tell you before you ask
- Ownership is written down. The contract states what you license and what remains ours, agreed before work starts rather than argued about later.
- We say no. If your problem is a process problem, more software will not fix it, and we will tell you that instead of quoting.
- Timelines are ranges. Anyone giving you an exact date for a system they have not scoped is guessing.
- Small team, real limits. We take on what we can support properly. Sometimes that means waiting for a slot.
- Your data leaves with you. If the relationship ends, you get an export in a usable format.
Under the hood
What we build with
Deliberately unfashionable choices. We pick tools we can still support in five years over whatever launched last month.
Start with the problem, not the solution
Send us what is going wrong in the business. That is more useful than a feature list, and it is usually where the real scope hides.