Aber Systems

~/software

Custom software development

Web applications, internal tools and integrations built around how your organisation actually works, and handed over with the documentation and access you need to keep running them.

Scope
Web applications, internal tools, integrations and APIs.
Starts with
A conversation, then a written specification and estimate.
Runs as
Short stages, each ending in something you can open and try.
Ends with
A live system, its source code, documentation and administrator access.

01 What we build

Three kinds of software, often in the same project

Off-the-shelf products are the right answer more often than developers like to admit. Custom software earns its place when your process is the thing that makes you different, or when the tools you have refuse to talk to each other.

A / web apps

Web applications

Browser-based applications for your staff or your customers: portals, booking and ordering flows, dashboards and record-keeping systems.

  • User accounts, roles and permissions
  • Responsive interface for phones and desktops
  • A data model designed around your records
  • An admin area for managing content and users
  • Deployment to a hosting environment agreed with you

B / internal tools

Internal tools

Purpose-built tools that replace shared spreadsheets, email chains and typing the same thing into two systems.

  • Forms and workflows that follow your real process
  • Approvals, status tracking and a history of changes
  • Import of existing data from spreadsheets or old systems
  • Reports and exports in the formats you already use
  • Access limited to the people who need it

C / integrations

Integrations and APIs

Connections between the systems you already have, so data is entered once and arrives everywhere it is needed.

  • Data synchronisation between applications
  • APIs for your own software, with documentation
  • Scheduled imports, exports and file exchange
  • Webhooks and event-driven automation
  • Logging and alerts when a transfer fails

02 Process

How a project runs

Six steps, each with something concrete at the end of it. Small projects pass through them quickly; large ones repeat the build step several times.

  1. Discovery

    We talk to the people who will use the software and map the current process, including the awkward exceptions.

    You receiveA short summary of the problem and the proposed approach.

  2. Specification and estimate

    The scope is written down: screens, data, roles, integrations, and what is deliberately left out.

    You receiveA written specification with an estimate and a staged plan.

  3. Interface design

    The key screens are sketched and agreed before they are built, while changing the structure is still cheap.

    You receiveWireframes or clickable mock-ups of the main flows.

  4. Build in stages

    Development proceeds in short stages. Each one ends with a version you can open on a test address and try.

    You receiveWorking versions and a running list of what is done and what is next.

  5. Testing and launch

    We test with realistic data and with your users, fix what turns up, migrate existing data and go live at a time that suits you.

    You receiveA live system and a record of what was tested.

  6. Handover

    The project closes with a walkthrough and everything needed to operate the software without guesswork.

    You receiveSource code, documentation and administrator access.

Progress you can read

At the end of each stage you get an update in plain terms: what is finished, what is being worked on, what comes next and what we need from you. No status meeting required to find out where things stand.

aber@systems: ~/project

aber project status

stagebuild, second stage of the agreed plan

donesign-in and roles · customer records · import from spreadsheet

in progressorder workflow · email notifications

nextreports · link to the accounting system

needs yousample invoices for the import test

test address open for your feedback

Illustrative example of a stage update, not a real project.

03 Deliverables

What you receive at handover

Software you cannot operate without its author is a liability. The exact list is set in the proposal; these are the items a handover is normally made of.

aber@systems: ~/project/handover

ls handover/

source-code/

documentation/

deployment-notes.md

admin-guide.md

access-checklist.md

head -1 documentation/README.md

# How to run, deploy, back up and restore this system

Source code
The complete code of what was built for you, in a repository you can access.
Documentation
How the system is structured, how to deploy it, and how to use the admin area.
Deployment setup
The hosting configuration, written down so the environment can be rebuilt if needed.
Access
Administrator accounts and credentials, handed over securely and listed so nothing is forgotten.
Walkthrough
A session for the people who will use and administer the system day to day.
Care plan
An offer for ongoing support and maintenance, if you want us to keep looking after it.

04 Questions

Common questions about software projects

If yours is not here, ask it directly: contact@vatutuexa.site.

Do you publish prices?

No. The cost of custom software depends almost entirely on scope, so a price list would be a guess. After the discovery conversation you receive a written estimate, and nothing is built until you have approved it.

How long does a project take?

It depends on the scope and on how quickly decisions and feedback can be given. The staged plan in the proposal shows the order of work, and you see progress at the end of every stage instead of only at the end.

Can you work with software we already have?

Yes. We start by reviewing what exists — code, hosting, documentation and access — and then tell you plainly whether it makes more sense to extend it, integrate with it or replace it.

What do you need from us?

One person who can make decisions, access to the people who do the work day to day, sample data that looks like the real thing, and timely feedback on each stage.

Who owns the software?

Ownership, licensing and access terms are written into the agreement before work starts, so you know exactly what is yours at handover.

What happens after launch?

Software in use needs care: updates, small changes, the occasional fix. That can be covered by our support and maintenance service, or handed to your own team together with the documentation.

05 Next step

Tell us what the software should do.

You do not need a specification to get in touch. A description of the problem and the people who have it is the right place to start.

aber@systems: ~/contact

mail contact@vatutuexa.site

problemwhat takes too long or goes wrong today

userswho would use it, and roughly how many

systemswhat it needs to connect to

timingany date that matters