Software that keeps working.
We build websites, online products and mobile apps for businesses. We also take on software that already exists and has become risky to run.
- Websites
- Customer portals
- Online shops
- Subscription products
- Internal tools
- Mobile apps
- Rescue and support
We are still here after launch
Most software does not fail on launch day. It fails slowly. A year later nobody can change anything without breaking something else, the person who understood it has left, and starting again begins to look cheaper than carrying on.
We build to avoid that ending, and we take on the businesses where it has already happened. The two halves feed each other. Fixing other people's software is the best possible education in what not to do in your own.
- Built for whoever comes next
- Written instructions, small changes that are easy to check, and decisions recorded with the reasoning behind them. If only one person can look after something, we have done our job badly.
- Everything in your name
- Your hosting, your web address, your app store listings, your accounts, from the first day. Leaving us should never be technically difficult, so we never make it so.
- We say no early
- If your project is too small for us, outside what we do well, or would be better solved without building software at all, you hear it on the first call and not three weeks in.
Four things, done properly
A short list we know well, rather than a long one we would be learning at your expense.
- 01Websites and Web AppsCompany websites, online shops, customer portals and internal tools, built so they stay fast and stay easy to change.6 to 12 weeks
- 02Online ProductsSubscription products and platforms, including the accounts, payments, permissions and behind the scenes work a product needs once paying customers arrive.3 to 6 months
- 03Mobile AppsApps for iPhone and Android, built once and released to both, including the parts most teams forget until the reviews arrive.2 to 4 months
- 04Rescue and SupportFor software that already exists and has become risky to run. We check it, tell you plainly what is wrong, fix what matters, and keep it working.Starts in days
The software nobody wants to touch
When we look inside software that was built in a hurry, the same problems come up again and again. Every one of these is quiet until the day it is not.
The keys are under the mat
criticalThe passwords to your system are sitting somewhere anyone who goes looking can find them.
There is no real backup
criticalEither nothing is being saved, or something is, and nobody has ever checked that it can actually be brought back.
The lock is on the wrong side of the door
criticalThe checks that decide who can see what happen on the customer's device, where a determined person can simply walk past them.
Faults happen quietly
highSomething goes wrong, nothing is recorded and nobody is told. Everything looks fine while orders or messages are being lost.
There is no undo
highChanges go straight to your live site with no way to reverse them quickly, so a small mistake becomes an emergency.
Everything is out of date
highThe parts your software is built from are years behind, several have known weaknesses, and catching up is now a project in itself.
No sales theatre
- 0130 minutes
Talk
You tell us the problem. We tell you whether we are the right people, including when we are not.
- 02Within a week
Plan
A written plan: what we will build, what we will not, how long it takes, what it costs, and the risks we can already see.
- 03Every week
Build
A working version on a private link every week, with a short written update. You watch it take shape.
- 04Your choice
Hand over or continue
Instructions and a walkthrough, then either your team runs it or we look after it. Both are fine.
What we hold ourselves to
These are not ambitions. Each one is a rule we follow on every project, and each one costs us something.
Nothing goes live without an undo
Every change can be reversed in one step, and we test that before launch rather than during an emergency.
Passwords are never left in the open
Not anywhere, and not at any point in a project's history. Where we take over software and find them exposed, changing them is the first thing we do.
Every alert reaches a person
An alert that only appears on a screen nobody opens is not an alert. If it cannot reach someone, it does not count.
We test where failure costs money
Payments, signing in, and anything that saves customer information. We do not chase a tidy looking score that measures the wrong thing.
Everyone can use it
People using a keyboard, a screen reader or a small phone can use what we build. It is checked automatically, not left as a step that gets dropped when the date gets close.
We tell you about our own mistakes
Straight away, in plain language, with what we are doing about it. Finding out later from your customers is not something we will put you through.
Small, and growing carefully
Altrazen is a small studio, and that is a decision rather than a stage we are trying to grow out of. It means the people you speak to are the people doing the work, and nothing gets passed through someone who has never seen your project.
It also means we take on fewer projects at a time than a large agency, and we turn down work that is not a good fit. If you want a team that will tell you when the answer is no, that is the trade.
What people actually ask
Because a number without a clear scope would mislead you. The same sentence describing a project can mean four weeks or four months depending on what already exists and what it has to connect to. You get a real, fixed number in writing after one conversation, rather than a range that quietly grows.
You do, once it is paid for, including everything produced along the way. It lives in your accounts from the first day, not ours. Hosting, your web address, app store listings and any other service are all set up in your name. Nothing about leaving us is made difficult on purpose.
A website or a focused web application is usually six to twelve weeks. A first release of an online product is three to six months. A mobile app is two to four months to the first store release. Checking existing software takes three to five days. Those are honest starting ranges. You get a real date in the written plan once we understand the job, and we would rather quote longer and be right.
Possibly, and we will tell you on the first call rather than three weeks in. A single page or a one day fix is usually better handled by a freelancer, and we will say so. Checking existing software is deliberately a small, self contained piece of work, so it is often the right first step if you are unsure.
You get written instructions and a walkthrough with whoever will look after it. Then either your own team runs it, or we keep looking after it for a monthly fee. Both are fine, and we will tell you which one we think suits you. What we will not do is disappear on launch day and leave you with something nobody understands.
Tell us what you need
Or what has already gone wrong. One conversation is usually enough to know whether we are the right studio, and we will tell you either way.