Web & SaaS
A product people log into. A system your team can run.
You send the brief. We build your web application or SaaS — people sign in and work, your staff can run it — then hand it over. We do not keep the product. Not a brochure site.
What you get
The product, not a pile of pages.
- 01
People sign in and do the work
Accounts, the right access, and the screens the product exists for — records, workflows, whatever the brief actually needs. How those screens work is part of this job, not a second design shop.
- 02
Your staff have a back office
The admin used after launch: users, content, and the day-to-day running of the product.
- 03
You own what we hand over
The result is yours. We stay through launch so that is not a surprise.
From brief to live
We don't stop at the first working screen.
We start by saying what the job is. Then we build it, put it online, and leave it in a state your people can operate.
- 01
Read the brief
A document, a call, or a sketch. We say what we will build, what we will not, and what done looks like — including a figure — before we write the product.
- 02
Build the product
Sign-in, the work users come to do, and the admin your team needs. If you charge customers, that can be in the same job.
- 03
Try it before customers see it
A private copy for you to click through. Then the live one. We do not ship by copying files by hand.
- 04
Keep it up
Hosting, backups, and a way to know if something is broken before users tell you.
- 05
Hand it over
Access, a clear picture of how it runs, and a launch you can own. You are not left with a black box.
Work we can show
FlowKan
A cloud Kanban product: workspaces, boards, cards, and filters. Teams see status without a heavyweight tool. This is one live web product we can show — not the shape of every job.
See the work
Questions
- Is this marketing websites?
- No. This page is for web applications and SaaS. A five-page company site is not the job.
- What should I send?
- Whatever you have: a document, a call, screenshots of a tool you already use, or a sketch. We do not need a finished specification. If the brief will fail, we say so while it can still be changed.
- What happens after I send a brief?
- We read it and tell you if we can take it. If yes, we say what is in the job, what is not, and what it will cost. Then we build. We do not start from a catalogue price.
- Can the same product include AI?
- Yes. Many web products have AI in them — generation, search, review, whatever the brief needs. That is still this job. If you only need the model, or the brief is not only a web product, send it anyway. We will say what we can take.
- Who owns the product when you finish?
- You do. The code, the accounts, and the live system are yours. We set hosting up so your team can operate it.
- Do you keep it running after launch?
- We stay through launch. After that you run it — or we stay on if that is in the scope we signed.
If the product lives in a browser, send that brief. We will say if we can take it.
Send a brief