Webvelopment
South Africa · Service area

Website Design & Software Development in Pretoria

A service website, WordPress rebuild or custom business workflow for a Pretoria-based team. We connect the public website with the people and systems that handle the next step.

Let’s talk

Websites and software your team can use

A retail worker at the counter of a small shop.
Illustrative photography · Vladyslav Hryhoriev / Unsplash

We can help with website design, WordPress development and custom software. Start with the part of the work that needs attention: helping customers understand a service, getting the right information into an enquiry, or reducing a repetitive staff task.

For example, a visitor should understand a service before sending an enquiry, and the receiving team needs enough detail to respond. We can use that whole task to shape the brief.

The Perforated Plastics website presentation offers an example of product information and enquiry design to discuss. It is a design reference here; the gallery does not establish a Pretoria client location.

A useful starting budget

The website planning model starts with 10 hours at R850/hour: R8,500 excluding VAT, including one standard page. For example, seven standard pages and one complex page give 10 + (6 × 3) + 6 = 34 hours, or R28,900 excluding VAT. This is indicative development labour; migration, integrations, content, hosting and supplier fees may add to the scope. Explore the website calculator.

The base includes the first standard page, leaving six at three hours each and one complex page at six hours. Bring a rough page list to discuss which pages fit those assumptions. Connections to other systems need a closer look.

Meetings and delivery

Remote workshops can walk through the current website or a staff task. Written reviews give colleagues time to check details against their own documents.

Any in-person meeting, travel and on-site access are agreed for your project. Contact details and business addresses are published together so you can confirm the appropriate arrangement before visiting.

Discuss your Pretoria website or software project with the current site, what needs to improve and your intended budget.

Bring the approval process into the project brief

The person explaining a service may need a colleague to check its technical claims, while someone else checks the enquiry form. Tell us who reviews each part so we can plan around those decisions.

Start with one customer or staff task. For a service enquiry, identify who can confirm the wording and who can check what happens after submission.

We can work with a Pretoria-based team through an agreed remote delivery process. Pretoria is the main business contact address listed on our contact page; please arrange meetings in advance.

Prepare material for a productive review

Bring the service descriptions, credentials and documents you use to answer customer questions. Mark anything outdated, awaiting approval or intended only for internal use, so we can see which facts belong on the website.

For an internal workflow, a sample form and a walkthrough of the task are useful starting points. Include an exception: what happens when a request is incomplete, needs a second approval or must go back for correction? Use redacted examples where information is sensitive, and agree access before sharing working systems.

Website services can make the offer easier to understand. Custom software can address an operating task once we understand its rules and who is responsible for the data.

Agree how the people will work together

Useful planning questions include:

  • Who brings together feedback from the Pretoria team and resolves conflicting requests?
  • Which decision needs a live discussion and which can be reviewed in writing?
  • Are any documents available only through an approved business system?
  • Is a site visit necessary, or can someone demonstrate the workflow remotely?
  • Who approves release, and who will look after the website or software afterwards?

If one reviewer asks for a shorter form and another needs more detail, settle which information the receiving team needs before asking us to change it.

Any in-person meeting, travel or site access is confirmed separately. Naming Pretoria in the brief does not confirm a meeting location.

Choose a bounded first phase

The first phase might be a content and structure review, a prototype or a defined implementation. If the service information is unsettled, begin there. If a staff task is hard to explain, a prototype can give the team something concrete to try.

Agree what your team will supply and how you will check the result. For an enquiry flow, an example check could follow a complete enquiry from the service page to the intended recipient, then try an incomplete submission. Any connections needed for those checks belong in the proposed scope.

Discuss your Pretoria project with the current site or workflow, the people who need to approve it and the practical review arrangements.

Questions for a Pretoria-led project

A few useful answers before you decide.

Can the first workshop be held remotely?
Yes, we can plan around agreed remote sessions and written reviews. Include someone who can demonstrate the task and the people who approve changes. Visits and premises access are arranged separately; naming the city does not establish an office or reserve a meeting.
What should a team with several approvers prepare?
List who checks facts, agrees the scope and confirms the software behaves correctly. Choose one person to bring feedback together and resolve contradictions. Give reviewers relevant documents with sensitive details removed, and a specific decision to make.
Can existing business documents inform the website?
Yes. Confirm that the documents are current and permitted for public use. An internal service document may help us write a shorter public explanation, while confidential instructions stay out of the page. Ask the person responsible for the service to check that the shorter version preserves its meaning.
How are decisions recorded between review sessions?
Use the agreed shared channel to say what was approved, by whom and whether it changes the work or cost. A comment such as “approved service wording; form fields still to be checked by the receiving team” is more useful than “looks good”. Keep suggestions separate from instructions to proceed so colleagues who missed the session can see what remains open.
What if the project depends on another supplier?
Tell us what the supplier controls, who owns the account and what information or access is needed. Your business may need to arrange that access. Permission to investigate does not authorise changes to a live system or bypass an existing supplier relationship. We can identify which proposed tasks can proceed and which must wait, so the estimate makes those dependencies visible.
What makes the first phase ready for acceptance?
Agree the task, approved information and example checks before implementation. Ask the reviewers to try the intended task and a relevant exception, such as an incomplete enquiry or a request that needs another approval. Check the content as well as the behaviour. The handover also needs an agreed recipient who understands what they will maintain and which items still need attention.

Create a review pack for a decision with several owners

Keep the pack small enough for each reviewer to use:

  • Link to the same version of the representative page or workflow, with the source material needed to check it.
  • Give each person a specific question, such as whether the service description is accurate or the enquiry contains enough detail.
  • Separate factual corrections, design feedback and requests that change the agreed requirement.
  • Bring conflicting feedback to the nominated contact before it becomes an instruction to us.

Flag anything still undecided, so reviewers can check the layout without treating an unconfirmed service claim as approved.

Prepare your next conversation

Send us the current website or the staff task you want to improve. Include who can check the facts, which documents are ready and your intended budget. We can use those to discuss a first phase with your Pretoria-based team.

Scope the website design decision · Scope a business software workflow

Discuss your Pretoria website or software brief.

Keep exploring

Keep the right things connected.

South Africa · Services

Digital Services for South African Businesses

Choose development, websites, marketing or creative services for your South African business by starting with the customer or staff task that needs to work better.

South Africa · Contact

Contact Webvelopment About a South African Project

Discuss a South African website, software, eCommerce, marketing or creative brief with Webvelopment, including goals, current tools and the people reviewing delivery.

Let’s move things forward

Start a conversation

Tell us what you are working towards. We’ll help you find a practical next step.

Let’s talk