Made by makers.

For OHS consultancies, occupational medicine clinics and in-house SESMT teams

A dedicated development team to build your OHS products

A RUDU squad builds what your OHS software doesn't: a client portal, eSocial integrations, field inspections and the workflow specific to your client portfolio. Monthly subscription, no lock-in.

Companies that trust RUDU

Why a dedicated team, not another software package

OHS software keeps the technical records. What sets a consultancy or clinic apart is everything else: how it serves each client, how it receives information, how it delivers documents and how it bills.

A dedicated team turns that way of working into a product, connected to what you already use.

  • Your workflow becomes a product

    The squad builds on the routine of your client portfolio, not on a generic template.

  • Your priorities

    You decide what comes first.

  • Continuous delivery

    Each part goes into use as soon as it is ready.

  • Keep your current software

    It integrates with your current OHS software, payroll and ERP.

  • No lock-in

    The team stays as long as it makes sense for you.

What the team can build

  • A client portal for the consultancy: PGR (risk management program), PCMSO (occupational health program) and technical reports with digital signatures and document expiry alerts.
  • Occupational exam scheduling between the client company and the clinic, with the ASO (occupational health certificate) and WhatsApp confirmation.
  • An eSocial S-2220 and S-2240 integration with an error queue and resubmission, connected to the client's payroll or ERP.
  • An offline field inspection app: checklists, photos, non-conformities and action plans.
  • PPE management: handover with digital signature, certificate of approval (CA) expiry and stock by work front.
  • Consultancy billing by contract or per covered worker, reconciled with the exams performed.

Did your system start with AI?

If your consultancy has already built a portal or its own tracking tool with AI, the team starts from it. RUDU also takes over systems built with AI tools such as Lovable, Bolt, v0, Replit, Base44, Cursor, Claude Code or ChatGPT, and makes them secure, reliable and production-ready.

See how we take over AI-built systems

What to expect from RUDU

After the free diagnostic call and once the contract is signed, the team is put together in 10 to 15 days. Before any code is written, you know what will be delivered, in what order and when. After the diagnostic week, every week brings at least one delivery for you to see and approve.

  1. First week: an approved diagnostic

    On day one, kickoff in the morning and planning in the afternoon. The first sprint is the technical and business diagnostic: the systems already in place, the integrations needed and the real demands. At the end of the week, you approve the plan, with priorities, dates and the infrastructure sized.

  2. A roadmap by quarter

    The plan shows the whole year, one delivery at a time, with the estimate in weeks and the month each one goes into production. The first quarter is detailed week by week. The following ones are indicative and gain detail at the end of each quarter, based on what the deliveries show.

    Sample roadmap

    1. Diagnostic: Q1 (Detailed week by week)
    2. Foundation: Q1 (Detailed week by week)
    3. Client portal: Q2 (Indicative)
    4. eSocial integration: Q2–Q3 (Indicative)
    5. Inspection app: Q3 (Indicative)
    6. PPE management: Q4 (Indicative)
    Illustrative example. Your roadmap comes out of the diagnostic.
  3. Foundation first, then each module

    The team first builds the base the whole product will use: access and permissions, integration with the systems you already have, audit trail, notifications, files and reports. Then each module comes in without refactoring what already exists.

    • Isolated failuresA problem in one module does not bring down the others.
    • No reworkA new module uses the same base.
    • Scaling of its ownWhatever has usage peaks gets its own structure.
    • Rollout by client or siteEach one sees only the modules it has signed up for.
  4. Every week, validated deliveries

    Weekly sprint cycle

    1. Monday morning:Week review. You see what is done and approve it.
    2. Monday afternoon:Planning the new sprint: what goes in and what waits.
    3. During the week:Building, with daily follow-up.
    4. Before each delivery:Full testing by the product manager.

    Fixes happen within the sprint itself.

  5. Everyone with a clear role

    The plan shows who does what and where each professional works in each quarter. The product manager runs the meetings, the testing and the validation with you. Architecture and technical review are done by RUDU. The team starts with one full-stack developer and one product manager and grows when the roadmap calls for it.

  6. Everything agreed in writing

    • The scope states what is and what is not in the proposal.
    • Limits come first: with a single person, for example, the team works on one front at a time.
    • When there is more than one path, you get the pros and cons of each so you can decide.
    • RUDU sets up the infrastructure, paid directly to the providers, with a cost estimate before work starts.
    • Monthly subscription, no lock-in.

What it costs

RUDU squads have a minimum starting cost of R$ 16,750.00 per month: that is the floor we work with. The minimum team is one full-time full-stack developer and one part-time product manager. The actual cost depends on the project scope. Monthly subscription, no lock-in.

What sets us apart: all the architecture is planned and built by RUDU. We architect your solution and lead the technical team; you only need to define the business rules and what you want to achieve with the product.

Minimum starting cost
R$ 16,750.00 per month
Book a free 30-minute diagnostic

Everything the team builds is yours

The code, the documentation and the product data belong to your company, not to RUDU. RUDU plans and builds; the result is all yours.

  • Source codeIn your company's repository, from day one.
  • Infrastructure in your nameServers and services contracted directly by your company; RUDU sets them up and configures them.
  • DocumentationWhat was built and how it works, so any team can carry it forward.
  • No strings attachedIf you end the subscription, the product stays yours and keeps running.

Who it's for

OHS consultancies and occupational medicine clinics that serve several companies, and in-house OHS services (SESMT) at companies with several sites, that need their own products and have no technology team.

Frequently asked questions

No. RUDU assigns a team that builds the product your company needs.

Book your diagnostic

In 30 minutes, you leave with a first outline of what the team can build for your consultancy.