Choose the application
Select the tool that solves your business priority.
- Read its public page and capabilities.
- Review the available entities and connections.
- Confirm that its scope matches your process.
From a need to a working app
Configure only what you need and start working in a few steps.
Suite.coffee combines a common commercial setup with onboarding tailored to every service. First you choose the app and plan; then you complete only the information required for that tool to work correctly.
Guided process
Four common decisions and configuration tailored to the app.
The journey avoids endless forms. Common steps create the instance; service onboarding prepares its first operating configuration.
Identify the instance
Give it a name and choose the country where that specific service operates.
- Country belongs to the instance, not the account.
- Timezone, currency and week start are suggested.
- You can manage other instances in different countries.
Select the plan
Start free or choose more capacity based on expected usage.
- Prices are common to every app.
- Limits depend on the service entities.
- Setup payment remains simulated in the current environment.
Complete onboarding
Enter the minimum operating information required by that app.
- Calendar asks for an initial service and schedule.
- Invoice configures the issuer and first series.
- Every new app defines its own minimum journey.
Configuration by country
Region is configured for each service, not once for the entire account.
A user may manage companies or locations in several countries. Each instance therefore records its operating context and uses it in calendars, amounts, documents and forms.
Timezone
Dates are shown in the instance timezone and safely stored in UTC where appropriate.
Currency
Every entity with an amount keeps its currency so historical values do not change with configuration.
Week and language
Week start and primary language adapt calendars, communications and the service experience.
Tax and region
Billing uses country and mandatory province or region where one exists to resolve applicable taxes.
Connectable applications
Share common entities without turning every app into one product.
Customers, contacts, professionals, catalog and business operations can be reused when two services need to work together. Connections define source, target, entity, direction and access level.
- Calendar can publish a business operation, but Invoice is the service that generates the invoice.
- CRM reads connected information without taking ownership of appointments, estimates or payments.
- Relationships can be one-to-one, many-to-one or many-to-many depending on the entity.
- Disconnecting a service does not automatically delete information from its owning domain.
Continuous control
Plan, usage and access level are always visible.
From My apps you can open each service, review its plan, see period usage and manage access. Managers only see what their role requires and limits apply to real operations.
Suite.coffee guide
Frequently asked questions
Do I need to configure every app when I register?
No. You create one instance at a time and complete only the onboarding for the selected service.
Can I have two instances of the same app?
Yes. Every instance has its own name, country, configuration, plan, users and data.
Can I connect applications later?
Yes. Connections are managed from the main customer area and only between compatible instances in the same organization.
Who can change the plan or access?
The instance owner controls the plan and additional users. Lower roles only see the functions they require.
What happens to my data when I change plan?
Data is preserved. When a downgrade exceeds capacity, affected items are reversibly suspended according to service rules.
suite.coffee
Choose a need and configure your first application.
The guided setup will take you from service selection to a minimum configuration that is ready for work.