Skip to content
Contact
Menu
RO

03 / WORK WITH US

Have something important to ship?

For your next release or software problem

A release to verify. A workflow to repair. A useful tool to build. Begin with a clear result and a documented scope—not an open-ended promise of hours.

Request a written proposal What a project includes

Scope, availability, cost and timing are agreed in a written proposal.

03 / WORK WITH US

What a project includes

We can discuss a focused tool, a bounded software repair or a release-quality review. Start with a defined outcome and a result that can be checked.

01

A release-quality review

Before your next release, understand what works and what needs attention.

Define the exact release and intended use, examine reproducible behaviour, and receive a prioritised account of findings and limits.

Scope and handover

Possible deliverables

  • Findings with reproduction steps and observed impact.
  • A record of the agreed checks, coverage and remaining gaps.
  • Retest notes for corrections included in the agreed scope.

A useful starting point

The version to review, its intended users and the journeys that matter most. Describe access needs without sending credentials.

Your written proposal confirms the deliverables, cost and timing before work starts.

Request a proposal
02

A software correction

A broken workflow or integration is getting in the way of useful work.

Start with a reproduced defect, agree a bounded correction, then retest the affected path. No production changes are assumed.

Scope and handover

Possible deliverables

  • A diagnosis tied to a reproducible problem.
  • The agreed correction and an explanation of what changed.
  • Retest results and handover notes for the affected workflow.

A useful starting point

What should happen, what happens instead, and the environment involved. Production changes require separate authorization.

Your written proposal confirms the deliverables, cost and timing before work starts.

Request a proposal
03

A focused tool

A repetitive task needs a small, focused application or automation.

Discuss a small application or automation, its users, environment and acceptance conditions. The deliverable and handover are agreed first.

Scope and handover

Possible deliverables

  • An implementation for the agreed task and environment.
  • Checks against the acceptance conditions you agreed.
  • Source or agreed deliverable, setup instructions and known limitations.

A useful starting point

Who will use it, what goes in and what should come out. Explain existing tools and constraints; begin without private files.

Your written proposal confirms the deliverables, cost and timing before work starts.

Request a proposal
04

Website delivery and improvement

An unfinished or awkward website needs a clearer path for its visitors.

Finish or improve a website, with agreed pages, devices, tested journeys and a useful handover.

Scope and handover

Possible deliverables

  • The pages and interactions agreed in the proposal.
  • Results from the agreed device, layout and visitor-journey checks.
  • A handover covering setup, updates and known limitations.

A useful starting point

The website or starting material, your audience and the action visitors should take. Tell us what needs to stay.

Your written proposal confirms the deliverables, cost and timing before work starts.

Request a proposal

Online purchasing is not available yet. Explore the details or send an enquiry.

What an engagement can deliver

What an engagement can deliver

Defined scope

The exact outcome, assumptions and exclusions are agreed before work.

Inspectable result

Source, a tested correction, or a documented assessment—according to the engagement.

Useful handover

Reproduction steps, setup information, limitations and the agreed maintenance path.

47NETWORK / 01 / EXPLORE

Software worth opening.

Try a public demonstration, play a case, or inspect an example of work in development.

PALIMATTER public demonstration interface

English-language demonstration. Plans still need physical checks.

Open the Workshop Inspect the saved example

A straightforward project process.

  1. 01

    Describe the problem

    Send the expected outcome and current situation.

  2. 02

    Agree what we will deliver

    Clarify access, deliverables, acceptance and commercial terms.

  3. 03

    Review the result

    Inspect the evidence and handover against the agreed scope.

Questions before you enquire

Can I purchase immediately?

Online purchasing is not available yet. You can request a proposal to discuss your project; an enquiry is not an order.

Is pricing fixed?

Each project is priced for its agreed scope. We discuss cost, timing and availability in the written proposal.

Will you repair my production system?

Only with the appropriate access, explicit scope and authorization. Testing alone does not authorize production changes.

Tell us what needs to work.

A short description is enough to begin. Do not include passwords, keys, private production files or other secrets.

Open the project email brief