# Software Company Website Example: Brightloop Software

Brightloop Software is an invented studio that builds custom web and mobile applications, and this sample shows how such a company can sell work nobody has scoped yet. The page explains what the team builds, prices a discovery sprint, splits the build into fixed price stages and ends with a quote form that asks people to describe the project in words.

Live sample: https://aiwebmaker.co/sample-websites/software-company-website-sample

Buyers of custom software are rarely technical, and they arrive worried about the final cost, a project that never ends and losing control of what they paid for. The sample meets the cost worry early by giving every kind of build a starting price and naming the first step, a two week discovery sprint at a fixed fee. The risk worry is handled by a short run of stages, each priced on its own and each with a point where the client can stop. Ownership appears in the opening facts and again in the questions, because a buyer who was locked in by a previous supplier will look for it. By the time a visitor reaches the form, the three biggest objections have been answered in plain words.

A software studio usually cannot show its best client work by name, so the page has to prove skill in other ways. A table matches common business problems to the kind of build that tends to solve them, which shows judgement instead of a sales pitch. The team section describes habits that matter years later, such as automated tests, code reviews and written records of decisions. Photos show workshops, prototypes and software in daily use rather than logos the studio is not allowed to publish. Example reviews are credited to job roles, which keeps the confidentiality the trade expects. Together these parts replace a portfolio wall with evidence a buyer can test in a first call.

## What is on this sample website?

| Page | What it is for | Sections |
|---|---|---|
| Opening view | Software shaped around the way you work | Request a quote; See how we work; Two weeks of discovery first; Fixed price per stage; Code, accounts and data owned by the client |
| What the studio builds | What we build | Customer portals; Internal tools and dashboards; Mobile apps; Integrations; Rescue and modernising; Support after launch |
| Project stages | How a project runs | Discovery sprint; Design and plan; Build in two week cycles; Launch and handover |
| Engagements | Three ways to work with us | Discovery sprint, $6,500 fixed; Fixed scope build from $28,000; Monthly team from $12,500 a month |
| Problem and build table | Which kind of build fits the problem? | Five common problems matched to a type of build and a typical first release |
| The team | Senior people from first workshop to launch | Repository owned by the client; Automated tests; Accessibility checks; Data region chosen by the client |
| Recent work | Inside recent projects | Scoping workshop; Prototype testing; Warehouse stock app; Operations dashboard; Code review; Launch week |
| Questions | Questions before a project starts | Ownership; How the price is set; Taking over existing software; Apps for phones; Where data is stored; After launch |
| Quote request | Request a quote or a call | Starting point; Kind of software; Rough budget; How to reply; Name and work email; Company; The project in words |

## Five things a cautious buyer checks before trusting a studio with custom software

### A paid first step with a clear end

Custom software is hard to price before anyone understands the problem, so strong studios sell a small fixed first step instead of a vague estimate. A discovery sprint with a set fee and a set length gives the buyer something concrete to agree to. It also produces something they keep, such as a prototype and a written scope, even if they go no further. Naming that step on the website filters out people who want a number for a whole system by Friday. A studio that sells its first two weeks honestly is far easier to say yes to.

### Stages a client can stop after

Large single quotes frighten buyers, and open ended hourly billing frightens them even more. Breaking the work into stages, each with its own price, lets a client commit to one piece at a time. The sample says this twice, in the process steps and again in the engagement cards, because it is the promise that removes the most risk. Monthly team pricing then covers clients whose product keeps growing after launch. When the money is easy to follow, the conversation can move on to what the software should actually do.

### Ownership spelled out before anyone asks

Many buyers come to a new studio after a bad experience, often one where the previous supplier held the code, the hosting or the app store accounts. A software company website should say plainly who owns each of those from the first day. The sample places ownership in the opening facts and repeats it among the questions near the end. Data storage deserves the same clarity, since privacy rules vary by country and buyers are asked about them by their own customers. Clear ownership is often the detail that turns a careful reader into a serious enquiry.

### Proof of skill without client logos

Confidentiality agreements stop most studios from publishing their best work, so the website has to show competence another way. A table of problems and suggested builds shows that the team looks for the cheapest fix, not the biggest invoice. Descriptions of working habits, such as fortnightly demos and tests on every change, give technical buyers something to probe in a first call. Photos of workshops and software in use carry the feel of the work without exposing any client. These signals together often persuade better than a row of logos would.

### A quote form about the problem, not the technology

Most people requesting custom software cannot describe a database, but they can describe the task that costs them hours every week. The form in this sample asks where they want to start, what kind of software they picture, a rough budget and how they would like a reply. A large text box then invites them to describe the project in words, with a prompt listing what helps. On AI Web Maker, a form of this kind comes with the first draft the builder writes from a few lines about the studio, and its labels can be reworded before launch. A form written in the buyer's language brings in requests that are ready for a real conversation.

## Frequently asked questions

### Who wrote the words on the Brightloop sample?

People on the AI Web Maker team wrote this studio's copy by hand, inventing Brightloop for the purpose, and its photographs came out of the platform's image engine. Your own pages start differently: the builder writes a first draft from the few lines you give it about your studio, and every price and sentence stays yours to change.

### Should a studio that builds to order publish prices at all?

Starting prices for each kind of build, plus a fixed fee for the first step, help buyers decide whether to get in touch. They also spare the team long calls with people whose budget could never fit. The final price still comes out of discovery, and the page says so.

### How do buyers reach a software company through its AI Web Maker site?

Every request comes in through the enquiry form on the page, which asks for a starting point, a budget range and a written account of the project. The studio answers by email or phone, and contracts and payment are settled between the studio and its client.

### What will hosting the studio's site come to each year?

Keeping the studio's site online costs $119 a year in hosting, or $19 monthly, while the domain is bought on its own from roughly 400 endings. Drafting and previewing carry no charge, so the first bill arrives on the day the site goes public.

Updated 5 November 2026 · AI Web Maker