Working with Panemeria

A clear proposal before work begins.

An inquiry starts a conversation. We use it to understand the problem, then agree the work, the cost, and how the result will be checked.

Discuss your project

The first conversation

Show us where the problem appears.

A page that no longer describes the business. A request that gets entered into three systems. A report whose totals do not agree. One concrete example is a useful place to start.

  • What happens now, and what you need to happen instead.
  • The website, tools, or reports involved.
  • Who will use the result or approve the work.
  • Any deadline, budget range, or existing commitment that affects the project.

You do not need all the answers before contacting us. Please leave passwords, customer records, and other confidential material out of the initial message. We can agree how to share anything needed for the work.

Agreeing the work

What the proposal should settle.

The written proposal sets the terms for your project. These are the points to resolve before committing to delivery.

Deliverables and boundaries
The pages, connections, reports, models, or findings to be delivered, including what is outside the project.
Price and payment
The pricing basis, payment schedule, and any subscriptions, licenses, or other third-party costs.
Timing and dependencies
Milestones and the access, source material, decisions, and approvals they depend on.
Review and acceptance
Who reviews the work, what is checked, and how feedback and included revisions are handled.
Changes during the project
How additional requests are assessed and how any effect on price or timing is approved.
Ownership and handover
Account control, rights to deliverables, files and documentation supplied, and any continuing support.

When the problem needs investigation first

An assessment can be a separate engagement. Its deliverable may be findings and a recommendation rather than a software build. Any implementation that follows needs its own agreed scope.

Explore business analysis

Accounts, access, and materials

Decide who controls each part.

Accounts and access

Before we work in a website or business system, we identify the account owner, billing contact, and access needed. The proposal should state which accounts you control and how our access is changed or removed at handover.

Files and rights

Ownership and usage rights are set out in the agreement. Custom work, existing tools, licensed images, and third-party software can have different terms. We identify the files you receive and any licenses or subscriptions needed to keep using the result.

Business information

We agree which data is needed for the project, how it will be shared, and any access or confidentiality requirements. Sample or redacted records may be enough for the initial review.

Review and handover

Check the work against the task.

Acceptance depends on what was commissioned. These are examples of checks a proposal can include.

A website update

Review the agreed copy and pages on mobile and desktop. Check navigation, contact links, and form behavior.

An automated workflow

Run a valid request, a missing-field case, a duplicate, and a failure. Confirm who handles anything that stops.

A report or planning model

Reconcile the inputs, inspect the assumptions, and repeat the calculation or refresh with another set of data.

Make the handover explicit.

Agree the files, account access, operating instructions, known limitations, and any training to be supplied. The person taking over should know how to use the result and where further work is needed.

After delivery

Support has its own scope.

Ongoing support can cover website updates, integration checks, report maintenance, or training. The agreement defines the systems and tasks covered, how requests are submitted, and any support hours or response expectations.

A completed project does not by itself establish unlimited maintenance or round-the-clock support. If a request falls outside the agreed coverage, its scope, cost, and timing need to be settled before work starts.

Explore ongoing support

Before you get in touch

Do we need a full project brief?

No. Describe the problem and the tools involved. We can work out which questions need answering before a proposal can be prepared.

Can we commission just the assessment or analysis?

Yes. A process review, reporting investigation, or planning question can be a standalone engagement. You can use the findings to decide what to do next.

Does this page replace the project agreement?

No. This page explains what to discuss. Your written proposal and agreement determine the deliverables, fees, rights, responsibilities, and support terms for the engagement.

Start with the problem you want to solve.

Tell us what is happening and what a better result would look like.

Discuss your project