Amagacho Tech Harrow · England

Home  /  Services

Two disciplines, four ways to buy them

Amagacho Tech Solutions Ltd is registered under two SIC codes — 62020, information technology consultancy activities, and 62012, business and domestic software development. This page sets out what each of those means in practice, what each engagement deliberately excludes, how the work is priced, and the work we turn down.

Book a scoping call What we do not do
§ 01 · SIC 62020

Independence is structural, not a slogan. We hold no reseller agreements and take no rebate, referral fee or resale margin. The fee is the same whatever we recommend.

Information technology consultancy

Consultancy here means answering a question you are already facing, in writing, with enough reasoning that you could argue with the conclusion. It does not mean a slide deck of industry trends. Every review begins with the systems as they actually are — including the spreadsheet everyone quietly depends on — and with the people who use them daily rather than only the people who signed for them.

Typical questions we are brought in for

  • Should we repair this system or replace it?
  • Should we buy a product or build something ourselves?
  • Is this supplier proposal reasonable in scope and price?
  • Why does our infrastructure cost what it costs?
  • What would it take to move this off its current platform?
  • Which of these three tools actually fits how we work?
  • What happens to us if this system fails on a Friday night?
  • Where is the manual work that software should be doing?

What a review produces

  • A written assessment of the current position, in plain English, readable in an afternoon
  • The realistic options — normally including “change nothing” — with the cost and disruption of each
  • Risks we can see, stated in terms of what would actually happen to your operation
  • A recommendation with its reasoning, so a technical reader can challenge it and a non-technical reader can act on it
  • A sequence of next steps that any competent supplier could carry out, not only us
The report is yours without conditions. It is written to be actionable by whoever you choose, and there is no clause anywhere obliging you to buy the implementation from us.
§ 02 · SIC 62012

Nothing is built without a written scope. What is included, what is excluded, the price and the date are agreed before the first line of code, and changes are re-scoped in writing.

Business and domestic software development

We write software that a business depends on to operate: the system that takes the orders, tracks the jobs, produces the invoices, or replaces four spreadsheets and an inbox. It is unglamorous work and it is where most of the value in small-business software sits. We build with mature, well-supported technology chosen so that another developer could pick the project up after us — not with whatever is fashionable this year.

What we build

  • Web applications and customer portals
  • Internal tools, dashboards and admin systems
  • Booking, scheduling and job-tracking systems
  • Integrations between systems that do not talk
  • Data migration off end-of-life software
  • Reporting and management information
  • Business process automation
  • Websites where the content genuinely changes

How the work is run

  • Fortnightly increments you can open, click and judge — not a status report describing progress
  • Your repository, your hosting account, your domain, from the first commit
  • Automated tests where they earn their cost, and a written note of where they do not exist
  • Deployment, monitoring and backups configured before launch, not afterwards
  • A written runbook and handover session so your team can operate it without us
  • Plain, current technology, so the next developer is not inheriting a puzzle
If a requirement is wrong, we say so early. The cheapest moment to remove a feature is before it exists. We would rather have an awkward conversation in week two than deliver something in week ten that nobody uses.

Ways to engage

Four shapes of work, priced before they start

Each shape has a defined beginning and end. None of them commits you to the next one, and each states the terms that apply to it.

01

Advisory review

A time-boxed look at a specific decision or an existing system, ending in the written assessment described above. This is the usual first engagement, and for a meaningful proportion of clients it is the only one they need.

  • Two to four weeks
  • Fixed fee, quoted before start
  • Interviews with day-to-day users
  • Report actionable by any supplier
  • No obligation to build with us
02

Project build

A defined piece of software against a written scope, with a fixed price or a capped estimate and a delivery date. Suited to work where the decision is settled and what remains is execution.

  • Written scope precedes any code
  • Fixed price, or capped estimate with the cap stated
  • Fortnightly inspectable increments
  • Handover, runbook and training included
  • Warranty period after launch
03

Retained advisory

A fixed number of days each month for organisations that need technical judgement available but do not need — or cannot justify — a full-time technical hire. In practice: reviewing proposals, sitting in on supplier calls, and being the person you ring before you sign.

  • Monthly, cancellable with notice
  • A named point of contact
  • Days used as you need them
  • No minimum term, no auto-escalation
04

Care and maintenance

Ongoing hosting, monitoring, security updates and small changes to a system we built or one we have reviewed and taken on. Optional in every case — a delivered project is complete whether or not you buy support for it.

  • Written schedule of what is covered
  • Flat monthly fee, no open meter
  • Response times stated in the agreement
  • Accounts remain in your name
  • Exit assistance if you move on
Pricing, in one paragraph. Advisory reviews and retained advisory are fixed fees. Project builds are fixed price against a written scope wherever the work can be scoped; where genuine unknowns exist we quote a capped estimate and state in advance what would push it to the cap. Nothing is invoiced before a scope is agreed in writing. The first scoping call is free, and it is not a discovery phase with a bill attached.

The sequence

What actually happens, step by step

The same six steps apply whether the engagement ends in a report or in running software. Each one produces something you keep.

Step 01

The call

Thirty minutes, free. You describe the problem; we ask what breaks, who it breaks for, and what it costs when it does. We say honestly whether it is work we can do.

Step 02

The look

A short, fixed-fee review of what you run today, with access to the systems and time with the people who use them. Time-boxed so it cannot drift into an open engagement.

Step 03

The recommendation

The written assessment: position, options, costs, risks and a recommendation with reasoning. Delivered as a document, walked through in a meeting, and yours to keep.

Step 04

The scope

If you choose to build: inclusions, explicit exclusions, price, date and payment schedule, written down and signed by both parties before work starts.

Step 05

The build

Fortnightly increments in your repository, deployed where you can use them. A short written note each fortnight covering what landed, what did not, and why.

Step 06

The handover

Credentials, documentation, runbook and a training session for whoever will run it. A warranty period follows. Ongoing support is offered, never assumed.

Boundaries

Work we turn down

A short practice is only credible if it is honest about its edges. These are the things we decline, and we would rather say so on a public page than halfway through a conversation you have already invested time in.

Where we can point you to someone better suited, we will — with no arrangement, fee or expectation attached in either direction.

  • Reselling software. We hold no reseller agreements and take no commission, so we cannot supply you with licences — only advise on which to buy.
  • Body-shopping developers. We do not place contractors into your team by the day with no accountability for the result.
  • Open-ended time-and-materials builds. If work cannot be scoped well enough for a fixed price or a capped estimate, we will say why rather than start the meter.
  • Work that needs certification we do not hold. Regulated environments with formal accreditation requirements need a supplier who holds them.
  • Rescues without a review first. We will not take over an unfamiliar system on a fixed price without first being paid to look at it properly.
  • Recommending something we would not run ourselves. Including where a client has already decided and wants the decision endorsed.

Your side of it

What we need from you

Engagements go wrong for predictable reasons, and almost all of them are about access and decisions rather than technology. None of the following requires preparation before the first call — it is what makes the work run once it starts.

What to put in a first email
One decision-maker
Someone who can approve a scope and settle a disagreement without convening a committee.
Access to users
An hour each with two or three people who use the system daily. This is where the real requirements are.
Honest constraints
The real budget range and the real deadline. Both change what we would recommend, and neither is negotiable by being hidden.
Timely review
Feedback on each increment within a few days, so the next one is not built on a stale assumption.
System access
Read access to the systems under review, arranged through your own security process — we will work within whatever that is.

Next step

Start with the question, not the specification

You do not need a written brief to talk to us. Describe the problem in your own words and we will tell you what shape of engagement fits it — or that it does not need one.

support@amagachotech.pro Contact details

Reply from a person within one working day