Process
Where information is created
List the steps it goes through, where information is created or added, and which current practices have to stay.
- Processing steps
- Where data is created
- Processes to keep
Apps & software
Custom software
Custom software
for your business processes
If standard software does not support your workflow, the missing functions can be developed for you, such as order management, searches or reports. We first agree which existing processes and data need to be retained.
AppsCraft handles the brief and follow-up. A development company or developer from our platform builds the system.
When custom makes sense
When standard software does not fit your process
Some needs come down to how you take orders, what products you handle or how departments split the work. An order might need its status, owner and documents linked together, and standard software may not follow the same steps you do.
Usually tied to
- How orders are taken
- The products you handle
- How departments share the work
Working out the brief
Work out what needs building
We take one real piece of work, such as an order, and follow it from start to finish in four steps.
Data
Which information to record
What gets typed in, picked or attached at each step becomes the system’s fields.
- Fields and formats
- Processing status
- Supporting documents
User roles
Who updates it, and what the next person needs to see
Each step records who’s responsible and what’s been said, so the next colleague doesn’t have to ask again. What each role can see follows how your teams split the work.
- Owners
- Correspondence
- Access for each role
Features
Confirm the development scope
Once the workflow, data and responsibilities are clear, we prepare a feature list, separate immediate work from later additions, and ask the development company to propose an approach.
- Feature list
- Priorities
- Development approach
Common areas
What usually gets built
You don’t need all four. Pick based on the problems you actually have.
Order records
Each order’s details, status and documents in one place, so you can see how far it’s got.
Correspondence & ownership
A record of who’s handling what and what’s been said, so someone can pick it up when a colleague is away.
Searches & reports
Find out what colleagues look up and which reports they produce regularly, then decide how to build them.
Existing tools
If an existing system is staying, check what data it can provide and whether it has an interface.
These are common examples. Which of them you need, and in how much detail, is agreed for each project.
Existing tools
Before connecting existing tools
If the new system has to share data with tools you already use, we check these three things before fixing the scope.
Available data formats
What data the current system can give us, and in what format.
Interfaces and data exchange
Whether there’s an interface we can use, and whether data needs to sync live or be exchanged at set times.
Assess first, then set the scope
The developers assess how the connection would work and how much effort it takes. The scope is confirmed after that.
Before you start
A few questions to think about
You don’t need every answer. The most useful thing is one real example, plus the spreadsheets you use now.
How the project runs
What happens
What happens
once we start
AppsCraft is your contact for the whole project. These are the usual four steps.
01Led by AppsCraft
Talk through a real example
We go through one real piece of work with you and talk about budget and timing. Anything not yet decided is noted to confirm later.
One real example
02Led by AppsCraft
Get a developer to assess it
We find a development company or freelancer on the platform with the relevant skills. They review the brief and propose an approach and schedule. Work starts after the project arrangements are agreed.
Developer proposes approach and timing
03Done by the partner
During development
Questions and changes come to us first. We sort them and pass them on, and check progress at each stage. If requirements change, we’ll explain the effect on scope, cost and timing before going ahead.
Check the impact before changing anything
04Led by AppsCraft
Check and hand over
We check the work against the agreed feature list, go through the handover list in the scope item by item, and note anything that still needs follow-up.
Checked against the feature list
Who we
bring in
We arrange a development company, specialist team or freelancer to take on the project, based on its scope and the skills required. AppsCraft remains your point of contact throughout the project.
Development companies & teams
For bigger projects that need several people, we agree staffing and the build plan with the company.
Freelancers & independent specialists
When the work is well defined and needs one particular skill, a freelancer can do it alone or join for one stage.
You might ask
Common questions
How do we decide what needs custom development?
Walk one real piece of work through: where information is created, who updates it, who picks it up. The steps standard software can’t handle, and that you don’t want to change, are usually the part to build.
Do we have to replace our existing systems?
Not necessarily. You can build only what the current system can’t do. For systems you keep, we check their data formats and interfaces first, then look at how to connect them.
We don’t have a full spec. Can we still start?
Yes. Bring one example and the spreadsheets you use now, and tell us which step causes the most trouble. As we talk, we’ll separate what comes first from what’s still open.
Who does the development?
A development company, specialist team or freelancer from our platform. AppsCraft finds the contractor, stays in touch with you, follows up progress and arranges delivery.
Who do we pay?
AppsCraft. Custom work varies a lot, so the stages and the price of each are agreed after the developer has reviewed the brief, and before anything is built. You pay for each stage before it starts, and the quote includes our service fee.
What if we need changes during development?
Tell us what you’d like to change. We check it against the agreed feature list with the developers, tell you what it does to scope, timing and cost, and carry on once you’ve agreed.
Custom business systems
Bring one real example
Bring one real example
and we’ll start there
You don’t need a full requirements document. We’ll start from that example and work out what needs building.