A familiar customer, missing context
Purchase history lives apart from contact details. Context disappears when responsibility changes.
1997 STUDIO / CRM
Know your customers. Simplify your day.
A CRM tailored to the way your shop works. Start with the customers, orders and stock workflows you need, then develop around your business.
The demo is a starting point, not the limit of your solution.
THE SMALL THINGS ADD UP
Busy all day. Still missing the full picture.
Are you asking again, searching again and re-entering information you already have?
More orders, more loose ends
Online and counter orders need reconciliation. The owner has to ask around to find unfinished work.
Data without clear answers
Stock and reports sit in separate sheets. Knowing what to do next takes another round of consolidation.
NOT JUST A STAFFING PROBLEM
The work is fragmented. Not your effort.
When everyone records work differently, information travels through messages, spreadsheets and memory. Another tool alone will not fix a disconnected workflow.
Studio starts by identifying where information gets lost, who owns the next step and what should be recorded correctly once.
A clear workflow. From customer to next action.
Agree on how information moves through your shop before deciding how many features to add.
- 01
Know the customer
Keep contact details and buying context together.
- 02
Follow each order
Know its status and who is responsible for the next step.
- 03
Review and act
Use agreed reports to identify work that needs attention.
A PRACTICAL STARTING POINT
Everyday tasks, ready to explore.
Customers
Contact profiles, customer lookup and quick creation during ordering.
Orders
Create orders, follow statuses and find processing details.
Products & stock
Catalogues, variants, inventory and store transfer workflows.
Operational reporting
Explore overviews and filters for understanding sales activity.
These are demo capabilities. Sample data does not represent business results or a live deployment.
BUILT AROUND YOU, NOT JUST THE TEMPLATE
Your shop should not have to fit a mould.
Studio can design and develop custom functionality after understanding your needs. More than a logo or colour change, it is about how the software supports your work.
Discuss your custom requirementsInformation
Fields, customer groups and the information your team needs to see.
Workflow
Order stages, handovers and approval rules.
Roles & reports
Access by responsibility and agreed reporting definitions.
Integrations
Existing data and external services, subject to technical assessment.
See the workspace. Not just an illustration.
Explore four screens captured from the working demo. Figures are sample data, not customer results.
See pending work and recent orders.
DESIGNED AROUND YOUR DAILY WORK
Your workflow. Your own CRM.
See how a florist, adviser or shop assistant could use a CRM tailored to their work. Three moments, three screens, with the fields and rules your shop needs.
The right bouquet. At the right time.
The shop’s problem
Orders arrive through messages and at the counter. Buyers and recipients differ; messages, approved designs and delivery times can get lost during handover.
A proposed working day, illustrated with fictional people and our real CRM demo. Custom field examples are interactive concepts, not screenshots of deployed customer systems. Final features and scope are agreed with your shop.
01
09:00 · Capture the request
A birthday order arrives by phone. The florist uses a laptop to record the buyer and recipient separately, set a budget and save the gift message on the order, ready for the maker.
1997 CRMOriginal demo screenshot
Designed around your shop
Studio designs recipient, occasion, message and delivery-slot fields around how your shop takes orders.
Explore the proposed custom fields and workflow
1997 CRMIndustry concept
A proposed workspace for your shop
Bouquet request · HOA-024
Recording request
- Buyer → recipient
- Sample customer A → B
- Occasion / budget
- Birthday · VND 650,000
- Gift message
- Wishing you a wonderful day!
- Delivery slot
- Today · 16:00–17:00
Try the button to see the proposed status change. Sample data only; nothing is saved or sent.
02
11:00 · Hand over to the maker
At the workbench, the florist opens the tablet to check the agreed design. The owner assigns the maker, sets a deadline and sees the preparation stage.
1997 CRMOriginal demo screenshot
Designed around your shop
Custom stages, ownership and checklists match your workflow, with photo approval where needed.
Explore the proposed custom fields and workflow
1997 CRMIndustry concept
A proposed workspace for your shop
Preparation · HOA-024
Awaiting work
- Assigned to
- Sample employee 01
- Design
- Seasonal flowers · Pink
- Checklist
- Design · Card · Wrapping
- Ready by
- Today · 15:30
Try the button to see the proposed status change. Sample data only; nothing is saved or sent.
03
15:30 · Check before dispatch
The florist checks the finished bouquet and card against the tablet record. Marking it ready lets the sales team know it can be handed to delivery staff.
1997 CRMOriginal demo screenshot
Designed around your shop
Design handover checks, approval rights and order history so the shop can retrieve the request next time.
Explore the proposed custom fields and workflow
1997 CRMIndustry concept
A proposed workspace for your shop
Handover check · HOA-024
Awaiting check
- Design & card
- Checked against request
- Recipient
- Sample customer B
- Delivery slot
- 16:00–17:00
- Future reminder
- Only with customer consent
Try the button to see the proposed status change. Sample data only; nothing is saved or sent.
What this workflow aims to improve
Sales staff, florists and delivery staff can refer to one agreed request instead of piecing together chats.
Your custom scope
Separate buyer/recipient, delivery slots, gift messages, design approval, assignments and reminders.
How to assess the result
Compare on-time deliveries, clarification requests and message/address errors before and after implementation.
Sell online or in store. Manage customers in one place.
Your website supports discovery and shopping. POS serves counter sales. CRM helps the team manage the information and work behind them.
You can start with CRM. Shared data, synchronisation and existing-system connections are scoped separately; you do not need the entire suite for one requirement.
EXPLORE BEFORE DECIDING
Don’t just read about CRM. Try a workflow.
Open the demo, try creating an order and explore customer lookup, products and statuses. Note what differs from your shop’s workflow to discuss with Studio.
Open the CRM demoUse sample data only. The demo is not your shop’s operational account.
Before writing code, understand the work.
Review, give feedback and agree on the approach before bringing the software into daily work.
Discover & scope
Review processes, data, users and priorities. Agree on deliverables, cost and milestones.
Design & review
Define screens, interactions and custom work. Review the approach before development.
Build & test
Implement agreed scope and test operational scenarios, access and sample data.
Handover & launch
Agree on migration, guidance and acceptance criteria. Support scope is recorded in the agreement.
SCOPE-BASED PRICING
Know what you’re paying for. Before starting.
You don’t need a complete feature list. Start with the most time-consuming problem and work with Studio to separate immediate priorities from later phases.
Core scope
Users, stores and required workflows.
Custom development
Additional screens, rules and reports agreed for your business.
Migration & integrations
Data review and the systems that need connecting.
Running & support
Hosting, maintenance, third-party fees and support, itemised in the proposal.
Questions worth asking before choosing a CRM.
Clarity at the start makes collaboration easier.
Do I have to use exactly what is in the demo?
No. It shows a starting point. Studio can scope and develop changes to screens, data and workflows for your needs.
Is all customisation included?
No. The proposal separates core functionality, custom development, integrations and ongoing costs. Changes outside the agreed scope are assessed before work proceeds.
Can I start without a website or POS?
Yes, we can discuss CRM on its own. Connections to existing tools depend on their data and integration capabilities.
Can you move my existing customer data?
We need to check the source format, quality and permissions first. Migration method, validation and cost are agreed before moving data.
What about access and sensitive information?
Discuss who needs access to which data, exports and reports. Access controls, backups and data handling requirements must be defined and tested in scope.
How long does implementation take?
Timing depends on workflows, custom development, integrations and feedback. Milestones are agreed after discovery; there is no single timeline for every shop.
What happens after I send an enquiry?
Studio reviews your needs and contacts you to clarify next steps. Sending an enquiry does not purchase software or commit you to an implementation contract.
START WITH A REAL PROBLEM
Tell us about your shop. Let’s simplify the work.
What do you sell, how many locations do you have, and what takes the most effort? Describe it as you would to your team. No technical specification needed.
An enquiry, not a purchase. You review your information before sending.