A task to improve
People re-enter information, follow inconsistent steps or need a clearer action. Describe the workflow and the result that would make it useful.
Explore development ↗Development · Publishing · Data
Software built
for what
comes next.
For business workflows and everyday use. Connect the application you need with its release requirements and the data behind it.
A working product has more than one layer.
Software development
Build around
the task.
Illustrative workflow. The visible screen rests on rules, permissions and changing states.
Look beneath the submit action
A request can require a description, an authorised user and a valid state before it moves to review. Those conditions belong in the specification.
Start with who uses the software and what they need to accomplish. A business application might organise requests, maintain structured records or support a customer interaction. A domestic application might help someone organise information or complete a recurring task.
These examples are starting points for discussion. Requirements can cover roles, validation, search, notifications and connections to other systems. Potential deliverables include interface flows, application code, relevant tests and setup documentation.
The right combination depends on the operating environment and the responsibilities agreed for the project.
Software publishing
Make the release
understandable.
A functioning application also needs a clear identity as a product: what it contains, where it works and how someone begins using it.
A publishing scope can cover distribution format, version naming, installation or access instructions, release notes and supporting documentation. Licence information, dependencies and an update route may also matter.
Store submission, commercial terms and ongoing publication responsibilities need their own agreement. Establish the release boundary before treating the package as complete.
A release is a set of agreed deliverables, with a recognisable version and a usable entry point.
Data processing & hosting
Give the data
a defined route.
Begin with the information available and the result required. Processing may involve importing records, checking formats, transforming fields or preparing an output for another system.
Input quality, exception handling and repeatability shape the work. Hosting adds decisions about where software runs, how access is managed and who responds when something fails.
What happens to incomplete records?
An agreed exception route can separate rejected records, explain the validation failure and define whether correction or manual review is required. The appropriate behaviour depends on the source and intended output.
| Layer | Decisions | Possible record |
|---|---|---|
| Application | Access, processing rules, failure behaviour | Configuration and operating instructions |
| Infrastructure | Provider, capacity, backups, recovery expectations | Environment and configuration record |
| Operations | Monitoring, response, maintenance boundaries | Agreed responsibility schedule |
Choose a starting point
Where does your
project begin?
A product to release
A defined audience needs a useful capability. Consider the application alongside the package, instructions and distribution requirements people will encounter.
Explore publishing ↗Information to move
Records need to cross formats, systems or operating environments. Identify the source, the destination and what must change between them.
Explore data work ↗Starting points can overlap. Name the main outcome first; then separate essential dependencies from optional additions.
A proposed working sequence
Turn an idea
into agreed work.
Review points and responsibilities belong in the proposal, where they can reflect the actual complexity.
Describe
Identify the users, current situation and intended result.
Define
Review constraints, agree deliverables and record acceptance conditions.
Build
Implement the scoped behaviour and resolve questions as they arise.
Review
Check working results against the agreed conditions and record open issues.
Handover
Confirm access, documentation and any separately agreed ongoing work.
Deliverables & acceptance
Agree what
completion means.
A useful specification links each capability to an observable result. It also records exclusions, dependencies and decisions that remain open.
Settle ownership, repository access, third-party licences and credential transfer in the agreement. The final list should match the commissioned work.
DevelopmentSource · setup · limitations
Illustrative acceptance condition: an authorised user can submit a complete request, while incomplete input produces a clear validation message.
PublishingPackage · version · release notes
Illustrative acceptance condition: the identified release can be accessed in its agreed environment using the accompanying instructions.
Processing & hostingRules · configuration · procedures
Illustrative acceptance condition: an agreed sample input produces the expected output, with invalid records handled through the documented exception route.
Possible scope, to be agreed for each engagement.
Before an enquiry
Questions worth
settling early.
Can a project use existing software?
Describe the current system and available access. Compatibility, licensing and change constraints need review before the scope is confirmed.
Must all three activities be commissioned together?
Development, publishing and hosting are distinct activities. A proposal should identify which are needed and how their dependencies connect.
What determines timing and cost?
Feature scope, integrations, data condition, review requirements and operational responsibilities influence the proposal. These need a project-specific assessment.
Is ongoing support included?
Maintenance, monitoring and response arrangements require explicit terms. A release or handover does not by itself define an ongoing service.
Company imprint
A clear company
identity.
KIRBY DIGITAL LTD
A private limited company incorporated in England and Wales on 30 June 2026. Company number 17309006.
Stated activities: business and domestic software development; other software publishing; and data processing, hosting and related activities.
Specific services, deliverables and responsibilities remain subject to agreement for each engagement.
Project enquiries
Tell us what
needs to work.
Outline the intended users, the task or product, and the outcome you want. Mention existing software, publishing requirements or data dependencies, plus a preferred timeframe if one is known.
An initial outline is enough to begin. Detailed requirements can follow as the scope becomes clearer.
Telephone+447425227187
Registered address106 POYNTER HOUSE 1 QUEENSDALE CRESCENT, LONDON, ENGLAND W11 4TB