Capture
What information is needed, and who supplies it?
Development and software publishing
Give software
a usable shape.
Business software. Domestic applications.
Software prepared for publication.
Start with what someone needs to do. We welcome enquiries about turning organisational tasks and everyday needs into a defined application, or preparing software for its audience.
Discuss a software projectOrganisational work
Give an operational task
a clear application.
Business software starts with the work people need to complete. An enquiry might concern collecting structured information, moving a request through review, maintaining a shared record or making a recurring task easier to follow.
Bring the current steps, the people involved and the exceptions that interrupt progress. These examples open a scope discussion; they are not a catalogue of existing products.
Check
Which rules and responsibilities guide a review?
Change state
What can happen next, including exceptions?
Return a result
What should the user understand or receive?
Everyday use
Make everyday software understandable.
Domestic applications serve personal and household tasks. An organiser, reference tool or focused utility begins with the same questions: when will someone open it, what will they expect to accomplish and how much attention should that require?
A useful brief describes the main action, the information someone enters and the result they receive. Readable language, accessible controls and understandable settings belong in that discussion before additional features expand the scope.
First useUnderstand the task
During useComplete one action
Returning laterRecognise what changed
Illustrative journey · The application and its behaviour would be defined for the particular project.
Software publishing
Prepare the software
and its explanation
together.
Publishing concerns how an application is presented and made available to its intended users. Identify the software, its audience, its present state and the proposed route to distribution.
Development and publication may be related, but each needs a defined scope. Compatibility, licensing, access arrangements and support responsibilities require explicit decisions.
Application
Establish what the software does and which version is being considered for publication.
Description and instructions
Explain the intended use, essential actions and information a person needs before starting.
Release information
Identify relevant changes and any limitations that users need to understand.
Distribution decisions
Agree availability, compatibility, licensing and installation or access guidance for the specific publication.
Define the deliverables
Name the handover.
An idea becomes easier to assess when its outputs are named. Agree each item individually: a demonstration answers different questions from a release prepared for wider use.
| Output | Purpose | Review question |
|---|---|---|
| Requirements outline | Describe intended behaviour and boundaries. | Does it cover the essential task? |
| Interface specification | Define actions, information and screen flows. | Can a user follow the journey? |
| Application and configuration | Provide the agreed working features. | Do they meet the acceptance criteria? |
| Findings and documentation | Record checks and explain operation. | Can responsibilities pass clearly? |
Ownership, hosting and maintenance arrangements need their own agreement; a feature description does not establish them.
Working towards a scope
A practical route
to agreed work.
Describe
Explain the problem, intended users and existing software. Identify the smallest useful outcome.
Agree
Clarify dependencies, responsibilities, review points and acceptance criteria before work begins.
Review
Assess behaviour against the intended task. Record decisions that change the work.
Confirm
Check the outputs and remaining responsibilities before handover or publication.
Timing, commercial terms and arrangements for later changes belong in the specific project agreement.
Behaviour under consideration
Specify the moments
between screens.
A screen is only part of an application. Requirements should explain missing information, changed decisions and actions that cannot finish. For each important task, establish a starting state, an expected result and a recovery route.
Request outline
Describe the task
A short, useful description
Illustrative interface · Not a company product
Ready
Make the next action and required information clear.
Incomplete
Explain what needs attention and preserve useful input.
Submitted
Confirm the result and explain what happens next.
Unable to finish
Describe the problem and an appropriate recovery route.
Before choosing a solution
Good questions.
Clearer boundaries.
What must connect?
Identify other systems and whether documentation or access is available. Integration scope depends on those conditions.
Where will it run?
Name the actual devices and environments. Platform coverage should be agreed explicitly.
What information is involved?
Describe personal or sensitive data categories without sending individual records in an initial enquiry.
Who will operate it?
Establish hosting, administration, maintenance and support responsibilities. Explain any deadline and the outcomes driving it.
Company particulars
Development.
Publication.
A defined purpose.
AETHERION SUBSTRATA LTD is a private limited company incorporated in England and Wales on 29 June 2026, with company number 17305681.
Its stated activities are other software publishing and business and domestic software development, recorded under UK SIC 58290 and UK SIC 62012.
A particular application's availability, project deliverables and ongoing service arrangements are established through the information and agreement specific to that work.
Begin with the task
Tell us what the
software needs to do.
Send a concise outline of the intended audience, the task, its current stage and any essential constraints. For existing software, explain what is already there and what needs to change.
Telephone4779947489
Registered officeFLAT 202, 3, PLATINUM COURT CEPHAS AVENUE, LONDON, UNITED KINGDOM E1 4FF