A website update
Review the agreed copy and pages on mobile and desktop. Check navigation, contact links, and form behavior.
Working with Panemeria
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 projectThe first conversation
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.
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
The written proposal sets the terms for your project. These are the points to resolve before committing to delivery.
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 analysisAccounts, access, and materials
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.
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.
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
Acceptance depends on what was commissioned. These are examples of checks a proposal can include.
Review the agreed copy and pages on mobile and desktop. Check navigation, contact links, and form behavior.
Run a valid request, a missing-field case, a duplicate, and a failure. Confirm who handles anything that stops.
Reconcile the inputs, inspect the assumptions, and repeat the calculation or refresh with another set of data.
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
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 supportNo. Describe the problem and the tools involved. We can work out which questions need answering before a proposal can be prepared.
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.
No. This page explains what to discuss. Your written proposal and agreement determine the deliverables, fees, rights, responsibilities, and support terms for the engagement.
Tell us what is happening and what a better result would look like.