On-demand builds

Software that fits the way your business works.

Custom software to replace fragmented tracking, connect systems and organize workflows. Scope, migration and ongoing operation agreed before delivery.

Project · inventory controlIllustrativeweek 6
  • Planned7
  • In build2
  • In review1
  • Live4
  1. Mon · 10:00REWeekly meeting with the people doing the work: the orders module comes first.
  2. Wed · 16:40TestsThe orders module passed its acceptance tests.
  3. Thu · 09:15RERenata approved the release.Approved · Renata

Remote projects for businesses in Brazil and internationally. We agree languages, working hours and visits as part of the scope.

The journey of a spreadsheet

A spreadsheet that became a system, module by module.

Illustrative · fictional people

Every delivery goes past the people who run the process before it goes live. The change history stays with you.

  1. week 1

    A plan in writing

    Scope, timeline, investment range and where the system will run.

  2. week 2

    First module in build

    Orders and stock, with the rules that live in the spreadsheet today.

  3. week 4

    Review with the people who use it

    “The batch column needs to show on the order.”

  4. week 5

    Fix and acceptance test

    The fix goes in and the module passes the agreed criteria.

  5. week 6

    ApprovalApproved · Renata

    Renata checks it and clears it for release.

  6. week 6

    Live

    The team works in the orders module. The spreadsheet steps aside.

Rules of the project.

Each rule goes into the plan in writing.

  • Scope in writing
  • Hosting set in the plan
  • Data and access in the contract
  • Weekly meeting
  • Acceptance test
  • Change log

Is this a fit for your business?

For businesses that have adapted to several tools and still need parallel spreadsheets to get essential work done.

  • The same information lives in different files with conflicting versions.
  • Important permissions, rules or integrations do not fit your current tools.
  • A critical routine depends on one person knowing every workaround.

What the implementation covers

A focused first release

We design with the people who use the process. The initial scope names the core task, roles, rules and acceptance criteria.

Data and integrations

We define data sources, cleanup, imports and access. Migration can happen in stages so the operation can keep working.

Delivery and continuity

The proposal specifies hosting, permissions, documentation, support, exports and usage rights. Maintenance ownership is agreed from the start.

Process demonstration

From enquiry to a reviewed proposal.

An illustrative example of connecting context and approval. Explore each step.

Intake

Someone asks for help organizing their business quotes. The record keeps the source channel and request, and receives an owner.

A local demonstration using fictional content. No customer, message delivery or external system is connected. A real workflow depends on agreed scope and confirmed integrations.

What we agree together

One initial workflow, with clear acceptance criteria

Project size depends on rules, integrations, users and migration. We compare an existing product, an adaptation and purpose-built software before recommending an investment.

What we need to understand

  • A walkthrough of the current work and relevant spreadsheets.
  • The roles that use, approve and administer the process.
  • Rules to preserve and essential integrations.
  • An owner who can prioritize and validate releases with the team.

Before you commit

When is custom software worth it?

When an important requirement remains poorly served by available products and there is enough value to maintain a system. Total cost includes implementation, maintenance, infrastructure and future changes.

Does the business control the software and its data?

Hosting, data control, exports, source code access and usage rights belong in the contract. We discuss these before you commit.

Can we start with one part of the operation?

Yes. A bounded process makes it easier to validate adoption and migration. Expansion follows observed results and agreed priorities.

Already running

Systems the house built and runs, live today.

Nellia runs its own house on the kind of system it sells. GudiSystem shows the reputation module at a fictional hotel, with illustrative data. Gestio shows the dashboard with fictional data. NelliaOS appears in its new version, with illustrative data.

NelliaOS · approval queueReviewby a person

Moving NelliaOS demonstration with fictional data. A request arrives on WhatsApp and Anjo prepares the reply. The review deck shows what goes to the customer, what changes after it is sent and what weighs on the decision. A person decides, the steps run through to the record and the desk clears. The same sequence repeats for three example companies, each with its own media kit.

Example with fictional data
GudiSystem · hospitality7modules in productionIllustrative scenario, fictional data
The GudiSystem reputation module at Hotel Estrela Imaginária. Illustrative scenario, fictional data.
Gestio · clubs and gymsPlaypublished appsIllustrative scenario, fictional data
The Gestio dashboard for Clube Horizonte Imaginário. Illustrative scenario, fictional data.
  • 2013building software since
  • +100clients with active systems
  • US$ 50Mthrough client operations
  • +25%average revenue increase for active clients

Figures from the group, reported by the group. The amount moved is what passes through the systems inside each client's own operation. Nellia's own revenue sits outside this count.

Start with the process that weighs most.

Tell us which routine still depends on a spreadsheet. The first conversation already shows what would go into the first module.

Custom software development | Nellia