Skip to content
Officera

The whole office
on one record.

Customers, contracts, payments, invoices, expenses and tasks share the same record. Mark a payment paid: the invoice comes into existence, the contract schedule moves on, and the balance changes. There is nothing to copy from one place to another.

7-day trial. A card is required at signup and the first charge lands on day 8. Cancel from the subscription area inside the app.

Payments

Where the money stands

Due this month€2,150.001 payment overdue
CustomerAmountStatus
Mendes & Lourenço, Lda.Monthly retainer · 3/12 · 2 Sep€450.00Paid
Quinta das OliveirasConsulting contract · 1/4 · 11 Sep€1,200.00Overdue
Tiago AbreuIndividual matter · 20 Sep€320.00Pending
Casa do Pão de VilarMonthly retainer · 8/12 · 1 Oct€180.00Scheduled

Demonstration data.

Features

Six areas, one record

Every area writes to the same tenant record. A customer entered once is already the customer on the contract, the payment, the invoice and the task.

  • Customers

    One page per customer

    Contacts, addresses, identifications, documents, activity history and financial history on the same page.

  • Contracts

    Contracts with a payment schedule

    A contract's payment schedule materialises as dated payments. Document templates with variables produce the contract from the customer's real data.

  • Financial

    Payments, invoices and expenses

    The payment owns the lifecycle. The invoice is the immutable document created when a payment becomes paid. Office expenses land in the same summary.

  • Tasks

    Board and calendar

    Draggable columns for people who work by state, a calendar for people who work by date. Same tasks, two angles.

  • Catalog

    Services and templates defined once

    The service catalog and document templates are defined once and reused across contracts and invoices.

  • Office

    Profile, users and permissions

    Office profile, users, role-based permissions, realtime notifications and the subscription, all in one administration area.

Up close

Three places where this shows

Financial

Money has a state, not a footnote.

A payment starts scheduled, turns pending, becomes paid or falls overdue — and that state change is what produces everything else. There is no separate place to record the invoice and another to record the receipt.

  • The invoice is generated the moment the payment becomes paid, and is immutable from then on.
  • Office expenses and income in the same financial summary.
  • Overdue payments are visible as a state, not as a report someone has to run.

Customers and contracts

From customer to contract without retyping.

The contract uses the customer that already exists, the services already in the catalog and the document template already written. What comes out carries the right data, because nobody copied it.

  • Identifications, addresses and contacts live on the customer page and reach the document from there.
  • Document templates with variables, sections and change history.
  • The contract's payment schedule generates the dated payments on the financial side.

Tasks

The work sits beside the record that created it.

Tasks live in the same tenant as the customers and contracts. Work by state on the board, work by deadline on the calendar.

  • Board with draggable columns and inline creation.
  • Calendar view over the same tasks.
  • Per-event notifications, delivered in realtime to whoever is in the office.

Pricing

Plans differ in seats. That is the whole difference.

Every plan carries the same complete workspace. Nothing is locked behind a higher tier — pick by how many people will use Officera.

Billing period

Starter

For a small office getting started.

€79/month

Seats5 seats

Choose

Growth

For a team that no longer fits in five seats.

€129/month

Seats10 seats

Choose

Enterprise

For the office with the most people working at once.

€199/month

Seats30 seats

Choose

Included in every plan

  • Customers, contacts, identifications, addresses and documents
  • Contracts, payment schedules and document templates
  • Payments, immutable invoices, expenses and the financial summary
  • Tasks on a board and on a calendar
  • Service catalog
  • Users, role-based permissions and notifications
  • Interface in Portuguese and English
  • Stripe billing portal to manage the subscription

Prices in euros. The seat limit is how many users the office can have active at the same time.

Prices shown from local configuration; the public catalog did not answer during the build.

Questions

What usually goes unsaid

How does the 7-day trial work?

You create the office with a card. Nothing is charged for the first 7 days; the first charge lands on day 8, on the plan and billing period you picked. Cancel before then and you are not charged.

Do I really need to give a card?

Yes. Signup ends in Stripe Checkout and the card goes on file before the office opens. Officera never receives or stores the card number — that data only ever touches Stripe.

Do the plans differ in any feature?

No. The workspace is identical across all three. The only difference is the seat limit: 5, 10 or 30 active users.

What happens if I go past the plan's seats?

Users above the limit can no longer sign in, and the reason is shown on screen. The data is untouched; switch plan or deactivate users to come back under the limit.

How do I cancel?

Through the Stripe billing portal, from the subscription area inside the app. Access continues until the end of the period you already paid for.

What is the office identifier?

It is the short name that separates your office from every other. It is proposed from the name you type, can be changed during signup, and is what identifies the office when signing in.

What languages does the app speak?

Portuguese and English. Both are maintained together, not one translated after the other.

Is there a mobile app?

No. Officera is a web application. It works in a phone browser, but it is designed for a long session at an office screen.

Can I export everything?

Not on your own yet. Contracts can be exported as documents today; a full export of the office's data does not exist and can be requested by getting in touch.

Security and GDPR

What is built, said without inflation

This section describes what the system does today. We do not claim certifications we do not hold, and we do not promise availability nobody contracted.

One tenant, one boundary
Every office is an isolated tenant. The separation is enforced by the database itself, with row-level security enabled and forced on the domain tables; the API refuses to start if the application role could bypass it.
Cards only at Stripe
Checkout and the subscription belong to Stripe. Card numbers never enter Officera's servers, and never appear in a form on this site.
Authentication and sessions
Passwords are stored with argon2id. The access token lasts 15 minutes and the refresh token travels in an HttpOnly, Secure, SameSite=Strict cookie scoped to the authentication path.
Data in the European Union
The application and its backups run on AWS infrastructure in eu-west-1 (Ireland). Daily backups are encrypted at rest and written by a write-only identity.
Who answers for the data
The office is the controller of its own customers' data; Officera is the processor, under Article 28 GDPR. The data processing agreement is published.
What we do not claim
We hold neither ISO 27001 nor SOC 2, we publish no uptime percentage, and we commit to no support response time. When those exist, they will be written here.

Signup

Create the office

Fill in the office and the first administrator. At the end you are sent to Stripe Checkout to leave a card. The 7-day trial starts when checkout completes.

Office

This is the name that appears on generated documents.

Used to sign in. Lowercase letters, digits and hyphens only.

The office's tax identification number.

Administrator

At least 12 characters.