01
Several contacts at one customer
A few people at the same company may get in touch separately. Company details and what each person said are best kept on one record.
Apps & software · CRM systems
Open a customer record
Open a customer record
and see where things stand
Customer details, enquiries, quotes and follow-up notes, all in one system. Your sales team can look back at past conversations or plan the next follow-up without hunting around.
AppsCraft finds developers or a software company on the platform to build the system. We remain your project contact and follow its progress.
Day to day in sales
Customer information ends up everywhere
Between receiving an enquiry and confirming the order, someone has to note what the customer asked for, the product details, each version of the quote and how every follow-up went.
01
Enquiry received
To record
Customer requirementsProduct details
02
Quotation
To record
Quotation versionsSupporting documents
03
Follow-up
To record
OwnerNext follow-up date
04
Order confirmed
To record
Follow-up progressCorrespondence
02
Enquiries about several products
Each product has its own enquiry, quotes and documents, and you need to know which quote goes with which product.
03
Searching for records when a colleague takes over
When records are kept in different places, whoever takes over has to dig back through old correspondence.
Common features
The usual parts of a CRM
Before work starts, we agree the CRM features you need and the requirements for each one.
Customers and contacts
One record per company
Company details, each contact and past correspondence sit on the same record. You can decide by role which colleagues see which customers.
May include
- Company records
- Several contacts per customer
- Correspondence history
- Access set by role
Enquiries and quotations
Every revised quote is kept
The enquiry, every version of the quote and the product details are linked on one record. When a customer asks what you quoted last time, you can find it straight away.
May include
- Enquiry details and customer requirements
- Product details
- Quotation versions
- Supporting documents
Sales follow-ups
Who owns it, and when to follow up
Each customer record identifies the person responsible, the next follow-up date and notes from previous conversations. A colleague taking over can review this history. Follow-up reminders can be added if needed.
May include
- Owner
- Next follow-up date
- Follow-up reminders
- Progress and handover history
Assignment and access
Access set by how your team splits the work
Customers can be assigned to named colleagues, and access to quotation history can be set by role. Assignment and access both follow the way your sales team works now.
May include
- Assigning customers to staff
- Access permissions by role
- Quotation histories
How we plan it
See how the information moves first
Before any development, we look at how you record customers and quotes today, then decide how the system should hold that information.
We usually take one real deal as the example and break it down into the fields to fill in, who handles it and what each person can see. After that, we talk to the developer about features and testing.
- From youThe spreadsheets you use now, the steps you follow and who will use the system.
- Written upA feature list with the process steps, data fields and permissions.
- DeliveredThe agreed features, plus the items on the handover list written into the scope. That can include the source code or repository access, admin access, user notes and test results.
What to prepare
Tell us how you work now
Say what’s most awkward and what you’d rather keep. We’ll use that to decide which features come first.
Four questions to start with
You don’t need every answer yet. We’ll fill in the gaps when we talk.- 01What do you use to track customers and quotes now?
- 02Who will use it, and what should it fix first?
- 03Do you have reference screens or a feature list?
- 04Any budget, timing or handover requirements?
Useful to bring
Current spreadsheets
Workflows
Who will use it
Reference screens or a feature list
How it works
How the project runs
AppsCraft agrees the scope with you, then finds a development company or freelancer on the platform to build it. Once work starts, questions from either side come to us, and we keep track of progress and handover.
01Led by AppsCraft
Write the brief
We go over how you work today and write it up as a feature list. Development and testing then work from that list.
You provide your current spreadsheets
02Led by AppsCraft
Confirm the development partner
Once the scope, existing technology and deliverables are settled, we bring in a development company or independent developer and agree the features and testing with them.
A company or one developer, as the work needs
03Done by the partner
Build & test
The partner does the development. When you’ve tested it and want changes, tell us. We pass them on and keep track of progress.
Testing arranged by AppsCraft
04Led by AppsCraft
Deliver & hand over
At delivery we check each item on the agreed handover list. Records are kept on file for later changes or a handover.
Deliverables as agreed for the project
Who does what
How we workYou prepare
- Current spreadsheets and ways of working
- The colleagues who will use the system
- Practices you want to keep
- Budget, timing and handover requirements
AppsCraft handles
- Writing up the brief and feature scope
- Finding a development company or independent developer
- Handling communication, progress and changes
- Arranging testing and handover
Partner handles
- Building the system to the brief
- Making changes after testing
- Delivering what was agreed
You discuss the requirements with AppsCraft and pay AppsCraft. We arrange the contractor and coordinate the project through delivery.
Bring the spreadsheet
you use for customers
No spreadsheet? Bring a reference screen or a problem you want solved, and we’ll start from there.