Large SwanLARGE SWAN / AUCKLAND, NEW ZEALAND
When spreadsheets and separate tools make work harder, custom software can bring the workflow together. We work with Auckland and New Zealand businesses to define what needs to be built and what an existing product can already do.
BUSINESS NEEDS
When customer records, order updates and approvals move through separate spreadsheets, teams can lose track of the current state. A shared business tool can bring the agreed records and steps into one workflow, with user roles and validation designed around the people doing the work.
Trade customers may need to browse their catalogue, submit orders or follow a request without sending another email. We assess those requirements against our mature B2B and ecommerce products, then define the customer-specific functions and connections that remain.
POS, online sales and ERP can each hold part of the same business process. We identify which system owns each record and how information should move between them, including what happens when a connection fails or data conflicts.
THE WORK
Plan internal tools, customer portals and web applications around the people using them and the tasks they need to complete.
Our mature POS, ecommerce, B2B and ERP products provide a starting point. We discuss the fit before defining any custom development.
Agree the systems to connect, the data involved and the handover and support requirements as part of the project scope.
DELIVERABLES
These are the areas to define when scoping the work. Included items and responsibilities are agreed before the project begins.
A clear list of users, workflows, required screens and checks for accepting the finished work.
The scoped business tool or portal, with only the system connections and data transfers agreed for the project.
Representative workflow checks and a reviewed approach to importing existing data when migration is included.
Operating guidance, access and ownership arrangements, and a defined scope for ongoing maintenance.
WORKING TOGETHER
Review the current steps and pain points. Compare them with existing POS, B2B, ecommerce and ERP capabilities before deciding what to build.
Confirm functions and integrations, review usable screens and test normal and exceptional workflows.
Review data, user access and acceptance, then agree deployment, handover and support responsibilities.
COMMON QUESTIONS
We first compare the workflow with our existing product areas. Custom work is scoped around the needs that remain.
We confirm the required functions, integrations, delivery approach and fees before work begins.
That is often the first option to assess. We compare your workflow with the existing product and scope the differences instead of assuming everything needs a new build.
We need to review their APIs, access conditions and data models. A connection is agreed only after those requirements and any third-party charges are understood.
Where migration is part of the scope, we review sample data, field mapping, duplicates and validation before the transfer. Source quality affects the work required.
Source-code ownership or product licensing, hosting access and maintenance responsibilities should be stated in the agreement. They depend on whether the project uses an existing product or a custom application.
AUCKLAND / LARGE SWAN