AS Tech ConsultingCrawley · honest IT conversationsTalk to us
Start a conversation

How we work, written down

You might be asking

How do we know you will do what you say?

Our straight answer

Because we write it down first, show you working software every fortnight, and let you stop whenever you want.

Our standards, in plain words

Everything in writing

After every meeting, a short note of what was agreed. Every phase begins with a written scope that also says what is not included.

Working software every fortnight

Not a report. Something you can tap or click, on your own device.

You own it all

Code, accounts, domains, designs. Registered to you from day one.

Accessible by default

WCAG 2.2 AA as our working target, checked before every release.

Security basics, always

Two-factor sign-in on admin accounts, regular updates, encrypted connections, passwords never in code.

A handover you can read

A guide written for your team, not ours: how it works, how to update it, who to call.

When things change

They will. We write down what the change means for time and cost before anyone agrees to it. Small adjustments within a fortnight are absorbed without fuss.

When we get something wrong

We say so, explain what happened and what we are doing about it, and fix it. Mistakes hidden become problems; mistakes admitted become lessons.

What "finished" means

It works on the devices we agreed, someone in your organisation has used it for real, it is documented, and you have said yes.

If a standard is not written down, it is a mood.

Contract terms are agreed in writing for each project; these standards describe how we intend to behave within them.