Rigi24 for Small Businesses: What Can You Start with for Free?

Small businesses usually need three things from software: simplicity, predictable cost and room to grow. Buying a large platform with dozens of menus and advanced workflows on day one is not always a sign of maturity. For a two- or three-person team, it can create more training work and more cost than value. Rigi24 Core takes the opposite approach: start with the permanent free foundation and add a module only when a real business problem justifies it.

For a shop, salon, clinic, training center, service office, repair company or consulting team, the right first question is “What do we actually need to manage better today?” rather than “How do we buy every possible feature at once?”

Why a modular model matters for a small business

A small company has limited money, management attention and staff learning capacity. Every new tool becomes useful only if it solves a measurable problem. The Core + Modules model allows the software environment to grow at the same pace as the operation.

At the beginning, a business may only need:

• a Business identity in Rigi24;
• a public page with correct information;
• one branch;
• up to three users;
• a basic dashboard;
• a simple customer directory;
• basic user access and permissions;
• basic Telegram Mini App access and system notifications.

Those elements belong to Core. Booking, Queue, CRM, WebRTC, AI, Store, Delivery and Invoice are separate modules.

Which small businesses can start with Core?

Any operation with one branch and a small management team can consider Core as a starting point. Examples include:

Salon or barbershop

Use Core for the public profile, opening hours, contact information, users and basic customer records. If the real issue becomes too many calls for appointments, Booking is the next module to evaluate. Do not try to turn customer fields into a homemade appointment calendar.

Technical service company

Keep the company profile and basic customer contacts in one environment and give two or three users separate accounts. If the team later loses track of follow-ups, tasks and customer context, CRM becomes relevant.

Clinic or consulting center

Core can provide the public business profile and basic customer contact directory, but it is not a specialized medical record system. Booking or Queue are independent modules if scheduling or physical waiting becomes the actual problem.

Training center

Use Core to present the business and organize basic contacts. A full LMS, school management system or attendance platform is a different category and should not be confused with Core.

Small shop

Core can establish the public presence and customer base. If product catalogue and order flow later become necessary, Store can be evaluated separately. End-customer online payment is not a standalone Rigi24 module; a custom website that needs payment can integrate the business's own payment gateway, with merchant and tax responsibilities remaining with that business.

What should you do on day one?

Spend the first session on the foundation rather than on feature shopping:

1. create the Business with the correct name;
2. add the official logo, phone, address, opening hours and description;
3. verify the first branch;
4. create a separate account for each user;
5. set basic roles and permissions;
6. start the Customer Directory with clean data;
7. review the public page on mobile and outside the administration panel.

How do you know when a module is worth buying?

Look for recurring operational symptoms rather than the number of features in a brochure.

| Daily problem | Module to evaluate | |---|---| | Too many calls/messages to arrange appointments | Booking | | Disorder and long waiting in a physical queue | Queue | | Forgotten customer follow-ups and tasks | CRM | | Need for direct web calling or softphone workflows | WebRTC | | High volume of repetitive questions | AI | | Need for product catalogue and order capture | Store | | Operational need to deliver Store orders | Delivery, which requires Store | | Need to issue/manage invoices | Invoice | | Usage-based outbound messaging | SMS |

The table is not an automatic recommendation engine. It simply connects a real problem to the module that deserves evaluation.

Example: why a salon should not buy everything immediately

Imagine a new salon with only a few customers each day. In month one, the valuable work may be completing the profile, creating a public link and keeping customer details organized. Buying advanced CRM, Queue, AI and WebRTC at the same time would probably create unused software.

Three months later, appointment calls may consume enough staff time that Booking produces a measurable return. At that point Booking is not “another feature”; it addresses a real cost. Apply the same logic to every module.

Starting cost for a small business

Rigi24 Core is free for self-setup and has no expiry. When one branch and up to three users are enough, the business does not need to pay a monthly fee simply to keep the base environment.

An optional 150 GEL on-site setup and training service is available if the team wants Rigi24 staff to configure the initial environment, train users and perform an on-site test. The charge is for the service work, not for the free Core entitlement itself.

Do you need a custom website immediately?

Not always. The Core public page can provide a structured link with essential information at the beginning. When the business genuinely needs multiple pages, custom design, SEO content, special forms or deeper integrations, the Rigi24 Business Website service can provide a custom implementation.

Rigi24 is not building a generic self-service website builder. The website is designed around the business and can connect to its active Rigi24 modules.

Use the trial as a decision tool

If you think Booking, CRM or another module may help but you are not sure, request a trial. The standard Rigi24 policy is a 15-day free trial for each Business + Module, subject to approval. It is not automatically activated.

Super Admin reviews the request. In justified cases an administrator can extend the total trial period up to 30 days. No payment card is required to begin the standard trial.

Do not waste the period just browsing menus. Define a real scenario and measure whether the module reduces calls, waiting time, missed follow-ups or another clear problem.

A practical first 30 days

Week 1: foundation

Complete profile, public page, branch, users and Customer Directory.

Week 2: real Core usage

Let the team work with the base environment and write down recurring operational problems. Do not activate modules just out of curiosity.

Week 3: choose one priority problem

Select one or two issues with the greatest impact—appointments, waiting, customer follow-up, communication or orders.

Week 4: targeted trial

Request a trial for the relevant module and define a simple success measure: fewer calls, less waiting, fewer missed follow-ups or faster response.

This keeps the software aligned with the business instead of forcing the business to adapt to unnecessary software.

When is Core alone enough?

Core may be enough for the current stage if you have one branch, a small team, need a public profile and basic customer directory, and your operational processes are still working well without specialist modules.

There is no rule that every business must buy something additional. Core should provide independent value.

When is Core no longer enough?

Consider the next step when a recurring issue becomes significant:

• appointments are being lost in calls and messages;
• physical queues create dissatisfaction;
• customer follow-ups are forgotten;
• repetitive calls/questions consume too much staff time;
• product orders need a structured workflow;
• the number of branches/users grows beyond the free starting scale.

At that point evaluate the relevant module and the real business scale.

Expensive mistakes to avoid

• buying several modules before defining the workflow;
• sharing one login among employees;
• keeping customer data only on personal phones;
• investing in a complex website before basic public information is correct;
• expecting software to automatically fix an undefined management problem;
• choosing based on feature count rather than a real use case.

Small-business decision checklist

• Is one branch enough right now?
• Are up to three users enough for the starting team?
• Is the business profile accurate and complete?
• Do you only need a basic searchable customer directory?
• Can you name the exact problem a paid module should solve?
• Can you test that problem during a trial before paying?
• Does the team have a person responsible for adopting the new tool?

Conclusion

For a small business, the best software is not necessarily the one with the most features. It is the one that is simple enough today and still leaves room for tomorrow. Rigi24 Core provides that free foundation: business page, one branch, up to three users, a basic Customer Directory and essential management access.

Every paid module should then enter with a clear business reason. If you have not set up Core yet, begin with the step-by-step setup guide. If you want to evaluate a paid feature first, read the Rigi24 module trial guide.

Start small and expand intelligently

Keep Core free and add only the module that solves a real daily business problem.

Start free

Frequently asked questions

Can a small business use only Core?

Yes. If the needs are profile, basic customer data and simple management, Core can be useful on its own.

Do I have to buy Booking and CRM together?

No. Modules are activated according to need, subject to genuine technical dependencies.

Can small businesses use trials?

Yes. Standard module trials are 15 days and may be extended to a total of 30 days with approval.

Does Core have a monthly fee?

No. Core is designed to be free and non-expiring.