CAP-04Software
Custom back-office software.
Small, focused applications for the gaps your main systems leave: trackers, approval tools, calculators and portals.
§ 01Overview
Overview
Every back office has a spreadsheet that has quietly become a system: a tracker for approvals, a calculator for arrears, a list of who has sent what. They work until the person who built them is away.
The proposed software work replaces those with small web applications: written down, tested, access-controlled and handed over with documentation.
Input
- The spreadsheet or process being replaced
- Users and their roles
- Systems to connect to
Output
- A working application
- Test cases and results
- User and technical documentation
- Change log
§ 02What it covers
Scope, line by line.
Requirement notes
Written with the people who will use the tool, in plain language, before any code.
Internal web apps
Trackers, approval flows, calculators and simple portals, with role-based access.
Integrations
Connections to your systems through files or APIs, so data is keyed once.
Testing
Test cases agreed before release and run on every change.
Documentation
User notes and technical notes handed over with the tool.
Maintenance
Fixes and small changes under a written scope.
Areas of operation
§ 03How it runs
The software line,
stage by stage.
The same five-stage discipline as every request: intake, validation, processing, review and delivery, shaped for this work.
§ 04Controls
Checks built in,
not added on.
Intended practice · to be confirmed
- Separate test and live environments
- Code under version control, reviewed before release
- Access by role, with sign-in events logged
- Personal data kept to what the tool needs
RolesWho does what
You keep
- Priorities and acceptance
- User access decisions
- Ownership as agreed in the scope
AKOS does
- Write the requirement note
- Build and test
- Release and document
- Maintain under scope
Personal data handled in this work follows the data-handling model on the How it works page.
§ 05Questions
Common questions.
Q01Who owns the code?
Ownership and hand-over of source code are set in the written scope for each piece of work.
Q02Can you build on our cloud or servers?
That is the preferred option where you have them, so the tool sits inside your own access controls.
MoreOther capabilities
Other proposed capabilities
Was this page useful?
Sends only this page's address and your answer. No personal data is collected.
NextEnquiry