Custom software for the way your business works
Growmoon builds custom software around a defined task, the people who do it and the systems they rely on. Bring us one workflow. We’ll help you decide what belongs in the first release and whether an existing tool already meets the need.

Define the workflow and who owns it
Walk through one real request from submission to decision. Who supplies the information? Who reviews it and who owns the result? A redacted example of a request or exception will help us see which records and systems your team needs to keep.
- Name the user, starting input and expected result.
- Record missing information, rejected decisions and escalation paths.
- Identify the person who will accept the first release.

Compare an existing tool with a custom build
An existing product may be suitable when its demonstrated workflow already fits the requirement. Configuration or a contained change may be enough. A custom build is worth evaluating when important roles, data relationships, exceptions or integrations cannot be represented acceptably. Compare these options against the same requirement, including the permitted use of components, access to source and the work needed to maintain changes.
Set a boundary for the first release
Separate essential work from later enhancements. In an illustrative purchase-request workflow, a requester submits information, an assigned reviewer makes a decision and an administrator inspects the history. The specification must still decide who may approve, what happens after an amendment and how a repeated decision is handled. This planning example is not a demonstration of a delivered application.
- List the roles and permitted state changes.
- Agree the essential journey and its exceptions.
- Keep additional dashboards, departments and integrations visible as separate scope.

Assign ownership of data and integrations
List the systems the application will read from or write to, the owner of each record and the access required. Identify migration categories and data-quality assumptions before estimating cleanup or transfer work. Compatibility depends on the actual systems, versions, interfaces and permissions. Use synthetic or redacted examples during scoping; account credentials and customer records need an agreed secure channel.
Write acceptance checks early
Write an acceptance example for each essential requirement. Include a valid journey and meaningful exceptions, such as missing data, an unauthorized decision or a repeated action. Record the expected result and the evidence needed to inspect it. A screen preview can explain an interface, but it does not establish that permissions, integrations or saved records behave correctly.
- Connect each requirement to an observable result.
- Name who performs acceptance and records feedback.
- Distinguish a defect from a requested scope change.
Essential journey agreed
Meaningful exceptions included
Evidence ready to inspect
Plan discovery, development and handover
Discovery can produce a workflow map, data dictionary, assumptions, exclusions and acceptance criteria. An implementation agreement should separately identify the designs, code, integrations, migration and documentation included. Agree repository and account access, deliverable ownership and third-party licence terms. Handover should also identify known limitations and the person responsible for operating the system.
Compare the build and ongoing responsibilities
The estimate depends on workflow complexity, roles, interfaces, data quality and acceptance requirements. Hosting, subscriptions, release work and continuing support need their own stated inclusions. For cross-border projects, agree meeting overlap, review milestones, response expectations and escalation responsibilities with the people who can make decisions. A first-release estimate should not silently become a promise to deliver every future phase.
Custom software handover
- Code and dependencies
- Delivered code, repository access and third-party licences.
- Accounts
- Access and operating responsibilities.
- Documentation
- Agreed deliverables and known limitations.
- Support
- Continuing support and change ownership.
Questions about custom software
What should a custom software discovery brief contain?
Describe the business outcome, users and roles, starting information, expected result, exceptions and existing systems. Add a realistic first-release boundary, ownership questions and an acceptance example for each essential workflow. Discovery documents and implementation work should be identified separately in the proposal.
Can an existing spreadsheet be the starting point?
Yes, a redacted spreadsheet can help explain fields, reports and the current process. It does not by itself define permissions, approval rules, data cleanup, integrations or exception handling. Explain how people use it and which decisions a replacement must support.
Does a custom build automatically include all source code and ongoing support?
Those terms must be agreed for the actual engagement. The agreement should identify delivered code and documents, repository access, third-party licences, account ownership and the scope of support. Do not assume that an existing product licence permits every modification or redistribution.
Tell us which workflow needs to change
Share one workflow, the roles involved, current systems and an exception you need to handle. Include first-release priorities, timing and budget context in your project message. Use redacted examples and keep credentials or personal customer records out of your message.
Discuss custom software scope