How a software company works
Who does what, where the money comes from, and where an intern fits.
A software company sells one thing: working software that solves a problem for someone who pays. Everything inside the company exists to find that someone, understand the problem, build the solution, and keep it running.
| Role | What they do every day |
|---|---|
Sales / business development | Finds clients, answers enquiries, sends proposals |
| Project manager (PM) | Plans the work, tracks dates, talks to the client every week |
| Business analyst (BA) | Turns what the client says into clear written requirements |
UI/UX designer | Designs screens and the flow a user goes through |
| Developer | Builds features, fixes bugs, reviews teammates’ code |
| Tester (QA) | Tries to break the software before the client does |
DevOps / support | Deploys, monitors servers, answers problems after go-live |
In a small company like ours, one person often does two or three of these jobs. A developer may join the client call, write the requirement and test their own work. That is why small companies are a great place to learn: you see the whole picture.
How the company earns
| Model | How it works |
|---|---|
| Fixed price | One price for an agreed scope. Extra features cost extra. |
| Time and material | The client pays for hours or days actually spent. |
Retainer / AMC | A monthly or yearly fee to maintain and support the software. |
Product / SaaS | Many customers pay a subscription for the same software. |
Every hour spent on rework, confusion or a bug that reached the client is an hour nobody pays for. Clear communication and careful testing are not "soft" extras. They decide whether a project makes money.
Your first week. The PM asks you to fix a spelling mistake on a client website. You notice the contact form also looks broken.