Remote delivery · Written deliverables

Choose a first deliverable you can review.

Choose a new build, focused improvement or ongoing care. The starting point is the job your website needs to do and the people who will maintain it after launch.

Small PDF document-tools website showing a real interface and clear task choices
Small-PDF.pro: actual screenshot of an independently owned development project. The public interface is available to inspect.

Relevant evidence before a proposal

Match the work sample to the feature you need.

An attractive homepage does not prove every capability. Small PDF gives you an interface to explore; Ratib Calculator shows Arabic input and results; EV Battery Guide shows reference content. These are independent projects, not client outcome claims.

  • For a service website, review navigation, evidence and the enquiry path.
  • For a tool, agree inputs, validation, outputs and the source of its rules.
  • For an existing WordPress site, review editing and compatibility in a separate scoped demonstration.
Explore the document-tool interface: small-pdf.pro

Compare three practical starting scopes

New service website

Bring one representative service, approved work examples and the information a buyer needs before contacting you. The first review covers page structure and the enquiry journey. Editing and content entry are priced explicitly.

Existing-site repair

Bring affected URLs and reproducible steps. The scope records diagnosis, backup, review access, acceptance checks and recovery arrangements. A redesign is considered when a smaller repair cannot solve the documented problem.

A custom web tool

Bring example inputs, expected outputs and the source of the rules. Agree validation and error states before additional features. Account, payment or external API requirements are separately identified in the proposal.

Business websites and web tools

For a service business, the priority may be explaining the offer and collecting useful enquiries. A web tool may need a calculation, filter or specific data workflow. We map that main task before choosing WordPress or custom code.

  • Planning: an agreed page list, navigation, content responsibilities and functional requirements.
  • Build: responsive templates, supplied content, contact links or agreed forms, and basic page metadata.
  • Review: mobile and desktop checks, key user journeys, working internal links and a list of launch requirements.
  • Handover: the access, source files and editing guidance specified in the proposal. Proprietary third-party products keep their own licence terms.

WordPress repairs and performance work

Send a few affected URLs and a description of what is failing. I review the theme, plugins, hosting constraints and the steps needed to reproduce the issue before recommending a repair or rebuild.

A performance task can include image sizing, font loading, caching, scripts and template changes. Before-and-after measurements should use comparable conditions. A laboratory score is useful evidence about a test, but it does not promise the same experience on every device or a particular search ranking.

Website care built around risk

A brochure site and a busy shop need different routines. The care proposal records which sites and software are covered, how changes are approved, and how an urgent issue should be reported.

Decisions recorded in a website care proposal
AreaWhat we agree before starting
UpdatesCovered software, update routine, test environment where available, and checks for forms or checkout.
BackupsFiles and database coverage, schedule, retention, storage location and a suitable restoration check.
SupportContact channel, working hours, response target, escalation process and any urgent work charges.
Content changesIncluded time or tasks, approval process, additional work rate and treatment of unused allowance.
ReportingA record of completed updates, checks, issues found and work that needs a separate decision.

Multilingual technical setup

A bilingual scope covers matching pages, navigation, readable layouts, language switching and the complete enquiry journey. Each published language has its own URL, with alternate-page signals for equivalent versions and form checks in both languages. Arabic work also needs right-to-left layout testing and careful handling of email addresses, phone numbers and mixed-language text.

You provide or approve the translated copy. Language review, legal review and responsibility for future translations are recorded in the scope. Tell me your preferred language for a scheduled project call so we can agree the arrangements in advance.

What needs its own agreement

Copywriting, translation, paid themes or plugins, hosting, stock media, payment gateway charges, product entry, email delivery services and ongoing SEO are included only when listed. A payment integration depends on your merchant account and provider availability. Revenue, advertising approval and search positions depend on the business, content, market and platform decisions. The agreement specifies the technical and editorial work to deliver.

Protect the useful parts of an existing site

Before replacing a website, identify its important URLs, enquiries and search landing pages. A migration plan should record redirects where URLs change, preserve useful content and test that pages remain accessible to search engines. An existing working site may need a smaller intervention.

Inspect a specific service scope

These pages explain deliverables, cost factors and acceptance checks in more detail: WordPress development, custom PHP tools and applications, multilingual website development and website maintenance.

For more inspectable independent work, explore Ratib Calculator for an Arabic interface and EV Battery Guide for reference content. The technology for your own project follows its actual requirements.

WhatsApp unavailable? Email me directly.

rjmuzu1@gmail.com
Email instead