Skip to content
Altrazen
Service

Websites and Web Apps

A website that still works well a year from now.

Usually six to twelve weeks, agreed after a first conversation
Why this matters

What usually goes wrong

Most websites are judged on how they look in the first week. The real bill arrives later. Pages that felt quick with fifty customers crawl with fifty thousand. A small change turns into a week of work. The one person who knew how to update it has moved on, and nobody else can. None of this is visible on launch day, which is why it keeps happening to good businesses.

What you end up with

  • A site that stays quick as your business grows
  • Changes that take hours instead of weeks
  • Something any competent developer can pick up later, so you are never stuck with one person
  • A safe way to undo a change if something goes wrong
What we do

Inside web work

  • Company and marketing websites

    The site your customers judge you by. Fast to load on a phone, easy for your team to update without calling a developer, and built so search engines can read it properly.

  • Customer portals and dashboards

    The place your customers log in to see their account, their orders or their data. This is where most of the real work sits, and where most of the mistakes get made.

  • Internal tools

    The screens your own staff use every day. Usually the least glamorous part of a business and the one where a few hours of work saves someone a few hours a week, forever.

  • Online shops

    Product pages, carts and checkout. We put extra care into payment, because that is the part where a small fault costs real money and nobody notices for days.

  • Speed and search

    Pages that load quickly on an ordinary phone on an ordinary connection, and that search engines can index cleanly. Both are measured before we call anything finished.

  • Moving an existing site

    If your current site sits on something that no longer fits, we move it across in stages, with the old one running until the new one is proven. No weekend where everything is switched at once and hoped for.

What you get

  • Everything we build, owned by you, in your own accounts from the first day
  • Written instructions any developer can follow, so you are never dependent on us
  • A way to publish changes and undo them in one step
  • Checks that run automatically before anything reaches your customers
  • A site people can use with a keyboard or a screen reader

What is not included

Saying this plainly saves everyone a call.

  • Logo design, brand identity or naming
  • Writing your marketing copy, though we will tell you where the words are doing the heavy lifting
  • Paid advertising and search marketing campaigns
  • Desktop software you install on a computer
Step by step

How this runs

  1. 01

    Understand the job

    What the site has to do, who uses it, and what already exists. If a smaller version would answer your question faster and cheaper, we say so now rather than after you have paid.

  2. 02

    Agree the plan

    A written plan covering what we will build, what we will not, how long it takes, and the risks we can already see. You approve it before any work starts.

  3. 03

    Build in small pieces

    Every week you get a working version on a private link and a short written update. You watch it take shape instead of waiting for a reveal at the end.

  4. 04

    Make it solid

    Speed checks, accessibility checks, backups, and a tested way to undo a bad change. This is part of the work, not a step that gets dropped when the date gets close.

  5. 05

    Hand it over

    Written instructions, a walkthrough with whoever takes it on, and everything transferred into your accounts. Leaving us should never be difficult.

Working together

How this is usually arranged

We do not publish rates, because a number without a clear scope would mislead you. You get a real, fixed figure in writing after one conversation.

Fixed price project

A defined result, a fixed price and a delivery date, all agreed before work starts. If you want something added later, it is priced separately rather than absorbed quietly or argued about at the end.

Best for

A well understood piece of work: a website, an app, a check of existing software.

Monthly support

A set amount of our time each month for looking after your software, making small changes and improving things gradually. It rolls on monthly, can be stopped with thirty days' notice, and always ends with a handover document.

Best for

Software that is live and needs to stay safe, up to date and working.

Questions

What people ask about this

Talk to us about this

Thirty minutes, nothing to prepare. We will tell you honestly whether we are the right studio for it.