Define what happens.
Development concerns the actions people can take, the information an application handles and the behaviour behind its screens. A useful brief explains the intended outcome as well as the steps that lead to it.
Software development + software publishing
Clear tasks.
Useful software.
Considered releases.
For business workflows and everyday routines. Start with what someone needs to accomplish; give the software a purpose worth defining.
Explore the possibilitiesAreas of work
Two activities.
One connected brief.
LASTMINUTESAI LTD brings together software development for business and domestic use with software publishing. The starting point is a practical question: what needs to work, and what needs to be ready for release?
Explain what is released.
Publishing concerns how software is prepared and presented for use. Product information, setup guidance and release details deserve attention alongside application functionality. Your enquiry can address either activity or both.
Business software
Give the task
a clear shape.
A proposed business application might help record requests, review information or coordinate work. These are possible project needs, rather than a catalogue of existing products.
Describe the complete journey: how work begins, what information is needed, who can change it and what counts as completion. Include exceptions such as duplicate submissions, missing information and actions requiring approval.
Requirements, interface designs, implemented functionality and handover documentation are possible deliverables to discuss. Their inclusion and acceptance criteria should be agreed for the particular project.
Domestic software
Built around
ordinary life.
Everyday software begins with everyday conditions. A proposed application might support a personal routine, organise information or help someone complete a recurring household task.
Explain the routine in ordinary language. Consider small screens, interruptions, understandable navigation and recovery from mistakes. Someone returning later should be able to recognise what they were doing and what remains.
A routine in view
Choose the next task
Review the details
Keep your place
Next taskContinue
Illustrative layouts: the same purpose can require a different interaction at a different size.
Software publishing
A release needs
its own explanation.
For a proposed publication, establish what is being released, who it is intended for and what someone needs to know before using it. Useful materials may include a product description, version identifier, setup instructions, compatibility information and release notes.
Distribution arrangements affect what is needed. Responsibilities for supplied content, third-party components, support enquiries and future updates should be discussed for each release. Availability and ongoing support belong in the agreement for that publication.
Project considerations
Make the boundaries visible.
Small details can change the shape of a software brief. Identify dependencies early, even when some answers remain open.
| Bring into the discussion | Why it matters |
|---|---|
| Intended devices and users | Screen sizes, access needs and working conditions influence interaction choices. |
| Existing systems and access | Integrations depend on available interfaces, permissions and who controls them. |
| Information being handled | Data types and formats help define storage, validation and handling requirements. |
| Ownership and future changes | Source-code handover, update responsibilities and documentation need clear agreement. |
A general description is enough for an initial conversation. Leave out passwords, confidential records and personal datasets.
Planning a project
From an idea
to an assessable brief.
Describe the outcome.
Explain the current task, the people involved and where the existing approach becomes difficult. Include a target date or preferred platform when either is relevant.
Separate the essentials.
Distinguish required behaviour from optional additions. Record constraints, dependencies and questions that need answering before development is agreed.
Agree what to review.
Define deliverables, review points and evidence of completion. Include release materials where relevant, with timing and commercial terms in the project agreement.
Before you enquire
A few useful answers.
Can an existing application be part of a project?
Describe its current condition, documentation and access arrangements so that the proposed work can be assessed.
Are platforms or support packages fixed?
Discuss your platform, delivery and support requirements in the enquiry. Specific availability and terms need to be established for the proposed work.
Does every project involve AI?
The company name does not establish a particular technology or product capability. Technology choices should follow the requirements of the application.
Can I discuss development and publishing together?
Yes. Both are stated company activities. Explain whether you need application functionality, preparation for release or a combination of the two.
Company information
The company behind
the conversation.
LASTMINUTESAI LTD is a private limited company incorporated in England and Wales on 22 May 2026. Company number: 17238403.
Its stated activities are other software publishing, UK SIC 58290, and business and domestic software development, UK SIC 62012. Individual project capabilities and arrangements should be established through correspondence about the proposed work.
Start a conversation
What should your software
help someone do?
Send a short outline of the intended users, their task and the difficulty you want to address. Mention whether your enquiry concerns development, publishing or both. You do not need a finished specification to begin.
Telephone4777777779
Registered office124 LASTMINUTESAI LTD., CITY ROAD, LONDON, UNITED KINGDOM EC1V 2NX