Skip to content
Sun Software logo with the tagline Engineering Beyond Code
Case Studies

Work that shows what was built and why it mattered.

Selected projects across product websites, ecommerce and digital platforms. Each one names the client, says what we built and links to the live result.

how-to-read8 projects
  • ClientNamed
  • What we builtDescribed
  • TechnologyStated
  • Live resultLinked
  • Results figuresOnly if verified
01

50+

Countries our clients come from

Mostly the US, UK, Germany, Canada and Australia.

02

1,685

Reviews on Fiverr

Public, and open for anyone to read.

03

16

People on the team

Working together since 2020.

04

4.9

Out of 5 on Fiverr

Average across all reviews.

Our work by service

Pick a category. Then a service.

Every project here is live, so you can open it and judge it yourself. Where a service shows “Coming soon”, we are still preparing its projects.

Web & Ecommerce

WordPress Development

About this service
Public case studies

Lessons from real projects, sorted by service.

162 public cases reported by others, each with its source. None of them is our client. Each one shows a problem we plan for in that kind of work.

Type

162 cases

  • IncidentsSecurity disclosure · 2025

    Lovable apps that let strangers read user data

    What happened

    A researcher scanned 1,645 apps built with Lovable. 170 of them had database rules that let visitors read user data without signing in. The builder's own scan only checked that a rule existed, not that it worked.

    What we do about it

    We test your access rules by trying to break them. A built-in scan is a start, not a review.

    Source: CVE-2025-48757 statement
  • IncidentsReported incident · July 2025

    An agent deleted a live database

    What happened

    The founder of SaaStr reported that Replit's AI agent deleted his live database and ignored an instruction to change nothing. Replit's chief executive called it unacceptable and began separating test and live databases.

    What we do about it

    Our agents never hold delete rights on live data, and destructive actions wait for a person.

    Source: The Register
  • IncidentsPublic health · October 2020

    15,841 Covid cases left out of a spreadsheet

    What happened

    England's daily Covid totals missed 15,841 positive cases over one week. Reports said the results were held in an old Excel format that silently dropped rows past its limit.

    What we do about it

    We replace spreadsheet hand-offs with a tool that checks its own data and warns when something is missing.

    Source: The Register
  • IncidentsMalicious package · September 2025

    A fake connector that copied every email

    What happened

    A package posing as Postmark's MCP server built trust over 15 versions. Then one update quietly sent a copy of every outgoing email to an attacker. Postmark itself was not breached.

    What we do about it

    We use official connectors, fix their version and review updates before they run.

    Source: The Register
  • Company reportsPublic service · March 2024

    New York's business chatbot told owners to break the law

    What happened

    An investigation found that New York City's official AI chatbot for business owners said they could take workers' tips and refuse tenants with housing vouchers. Both are illegal. It also gave different answers to the same question.

    What we do about it

    We test the AI's answers against real questions before launch, and keep testing after it.

    Source: The Markup
  • Courts & regulatorsCourt sanction · June 2023

    Lawyers filed court cases that did not exist

    What happened

    In Mata v. Avianca, lawyers filed a brief written with ChatGPT that cited court decisions that were never made. A New York judge sanctioned them with a $5,000 penalty.

    What we do about it

    Our assistants answer only from your real documents and show the passage, so every answer can be checked.

    Source: CNBC
  • IncidentsTrading · August 2012

    $460 million lost in 45 minutes

    What happened

    A faulty software release at Knight Capital sent more than 4 million orders in 45 minutes. The firm lost more than $460 million. The regulator found that automated warning emails before the market opened were not acted on.

    What we do about it

    Our automations have limits on each run, and a person is alerted and expected to act when one fails.

    Source: US Securities and Exchange Commission
  • Courts & regulatorsLawsuit · June 2025

    A solar company sued over an AI summary about a lawsuit it says never existed

    What happened

    A Minnesota solar business, Wolf River, sued Google. Its complaint says Google's AI Overview stated that the state Attorney General was suing the company, and that none of the pages the summary cited said so. The complaint lists customers it says cancelled. Nothing had been decided when this was reported.

    What we do about it

    We record what AI tools say about your company at the start, and make your own facts clear and consistent so there is a correct version to find.

    Source: The Volokh Conspiracy, Reason
  • Company reportsGovernment trial · June 2025

    20,000 UK civil servants tried an AI assistant for three months

    What happened

    The UK Government Digital Service gave 20,000 staff in twelve organisations a Microsoft 365 Copilot licence. Users reported saving 26 minutes a day on average, a figure the report notes is self-reported. Use was high in Teams and low in Excel and PowerPoint. The report said training was essential to get the benefits.

    What we do about it

    We train each role on its own tasks, so use does not stop at the easy ones.

    Source: GOV.UK, Government Digital Service

Showing 9 of 162

How to read them

What each example tells you

You need more than claims about tools. You need to see how a problem was approached and what was delivered.

What you will not find here

Invented results, borrowed logos or anonymous quotes. If the evidence or the permission is missing, we leave the claim out.

  • Who it was for. The client, their sector and, where relevant, their market.

  • What we built. The site, store or platform, and the features that mattered.

  • The technology. The stack we actually used, not a list of everything we know.

  • Where to check it. A link to the live result.

  • Results. Figures appear only when the client has measured them and approved their release.

Client review

In a client’s words

“Thank you! SunSoft resolved a technical login issue within 30 minutes, guiding me step-by-step via call. They explained the cause, implementation, and future prevention. Absolutely amazing work—professional, thorough, and highly recommended for technical support and website solutions.”

digitalproseo · Australia · Fiverr review

A website login fault needed fixing quickly. We diagnosed it on a call, resolved it within 30 minutes, and explained the cause and how to prevent it.

Behind each project

Want the detail behind a project? Ask us.

A card shows the result. On a call we walk you through how a project was planned, built and tested, within what each client allows us to share.

Three projects have a full case study so far. More are added as clients approve them.

  1. 1

    The challenge

    The starting point, the constraints and what the client needed.

  2. 2

    The decisions

    The options we considered and the trade-offs behind the choice.

  3. 3

    The validation

    How the work was tested, released and accepted.

  4. 4

    The outcome

    What was delivered, and measured results where the client has approved them.

FAQ

Questions about our work

Can we see work relevant to our platform?

Each card names the technology used. Tell us your platform and we will point you to the closest example, or say plainly if we do not have one.

Why are there no results figures?

We publish numbers only when the client has measured them and approved their release. Until then we describe what was delivered.

Will our project appear here?

Only with your written permission. Many projects stay confidential.

Do you sign an NDA?

Yes. We sign one before you share code, data or access.

Where is the delivery team located?

Engineering and project delivery are managed from Pakistan for international clients. Your engagement documents name the company you contract with.

  1. 1Describe the challenge
  2. 2We ask the right questions
  3. 3You get a clear next step

Have a similar project?

Describe what you need to build or fix. We reply within one business day, tell you which of these projects is closest and suggest a first step.

  • The first conversation is free
  • NDA before you share anything
  • A reply within one business day