The best way to start with Kataboom is not to activate everything. Begin by creating trustworthy business context, identify the current priority and then prepare the product responsible for that workflow.
This sequence reduces duplicate setup and gives the team time to understand ownership, permissions and expected outcomes. Every product is available, while deployment scope, provider connections and plan inclusion are confirmed during activation.
Key takeaways
- Create the company workspace before product activation.
- Use an assessment when the business priority is unclear.
- Prepare clean data and named owners before configuration.
- Test one complete workflow before wider rollout.
Step one: create and verify your account
Use an email address controlled by the person who will manage the first company workspace. Complete verification and protect access with the available security controls.
Avoid shared accounts. Named users create a clearer audit trail and make it possible to assign suitable roles as the team grows.
Practical actions
- Use accurate personal and contact information.
- Verify the account before company setup.
- Keep recovery information current.
- Invite colleagues through their own accounts.
Step two: complete company onboarding
Company onboarding records the identity and operating context that Kataboom products share. Prepare the business name, industry, model, address, primary contact and current selling channels.
Review public facing details carefully because they may later support receipts, Storefront or Yellow Pages. Selecting a channel expresses intent, but it does not silently connect a provider or activate a product.
Practical actions
- Confirm company and primary location details.
- Choose the business model and relevant capabilities.
- Name the accountable primary contact.
- Review all information before creating the workspace.
Step three: assess the business when the priority is unclear
An assessment helps turn a broad concern into an explainable starting point. Answer with current evidence, not the answer the business hopes will look best.
Review the factors behind the result and choose a recommendation that the team can own. An assessment supports judgement; it does not replace professional advice in regulated areas.
Practical actions
- Choose the assessment that matches the decision.
- Use current operational information.
- Review gaps and recommendations together.
- Assign the selected next action.
Step four: choose the product responsible for the problem
Use Command Centre for assessments and wider oversight, POS & Inventory for sales and stock, Storefront for online commerce, Yellow Pages for local discovery, 360 Marketing for permission aware engagement and Field Sales for distributed selling activity.
Select the smallest scope that can create a meaningful outcome. Confirm deployment, plan and integration requirements before activation.
Practical actions
- Match the product to one priority workflow.
- Confirm who owns setup and daily use.
- Review data and permission boundaries.
- Agree what success will look like.
Step five: prepare information and people
Software setup is easier when data and responsibility are ready. Clean product records, customer details, location information and staff access before import or connection.
Train the people who perform the work, not only managers. Give each role the least access required and explain how exceptions should be handled.
Practical actions
- Remove obvious duplicates.
- Confirm locations and catalogue units.
- Assign roles and responsible owners.
- Document the current workflow and exceptions.
Step six: test one complete workflow
A successful login does not prove the business process works. Complete a controlled scenario from beginning to end and check every important state.
For POS this may be a low value sale and receipt. For Storefront it may be an order, payment outcome, inventory reservation and fulfilment. For marketing it may be an eligible audience, approved provider and suppression check.
Practical actions
- Use a safe test case.
- Check owners, amounts, states and audit details.
- Test failure and cancellation behaviour.
- Record and resolve gaps before launch.
Step seven: review value before expanding
After activation, compare the new workflow with the original problem. Look for improvement in control, speed, accuracy, customer experience and management effort.
Add another product or channel only when the current workflow is understood and the next need is clear. Connected growth should reduce blind spots, not multiply them.
Practical actions
- Review the agreed success measures.
- Collect feedback from daily users.
- Close configuration and training gaps.
- Choose the next improvement deliberately.
Frequently asked questions
Clear answers for the next step.
Which Kataboom product should I activate first?+
Activate the product responsible for the most important confirmed problem. If the priority is unclear, begin with Command Centre and an assessment.
Do I need every product to use Kataboom?+
No. Products are modular. Start with the smallest useful scope and add another product only when it solves a clear business need.
Does onboarding connect payment or social providers automatically?+
No. Company onboarding records business context and preferences. Each provider connection keeps its own authorisation, approval and testing process.
Put the guidance into practice
Create the business context first.
Follow the detailed onboarding guide, then continue through the product guides in the recommended order.
