For digital agencies
We handle the development while your agency manages the client.
Agencies often win work that needs more development than the team can take on, or a kind of development it doesn’t usually do: a booking system, a customer portal, or a Next.js build of a design the client has already approved. That’s where we come in.
You keep the client, the pricing and the project management. We build the part you’ve handed us, in your accounts where possible, and only talk to your client if you want us to. Confidentiality and how the work is credited are agreed with you before we start.
Agencies at capacity
You’ve signed the project and agreed a timeline, but your developers are busy. You need someone who can start without weeks of onboarding.
Design-led agencies
Brand, UX and interface design are your strengths. You want a team to build what you design, including the application behind it when there is one.
Agencies asked for something new
You build marketing sites well, and now a client wants a customer portal, a booking flow or a link to their existing systems.
This is how the work is usually split. We confirm the details with you before we start.
| Responsibility | Your agency | fullstack.sg | Note |
|---|---|---|---|
| Client relationship and contract | Yes | No | We don’t contact your client unless you ask us to. |
| Pricing and invoicing the client | Yes | No | Usually we invoice you and you invoice your client, though we can invoice the client directly. |
| Design and content | Yes | No | We’ll point out anything that’s hard or costly to build. |
| Scope decisions | Yes | Yes | You decide; we explain the technical consequences. |
| Technical approach | No | Yes | Written up so you can explain it to the client. |
| Development | No | Yes | Your developers can review our code. |
| Testing and sign-off | Yes | Yes | We test against the scope; you and your client sign it off. |
| Hosting and third-party accounts | Yes | Yes | Held by you or your client; we set them up with the access you give us. |
| Maintenance notes | No | Yes | Written for whoever looks after the project next. |
Before your client signs, we review the brief or designs and send an estimate that lists what it assumes and what it leaves out. Your proposal is then based on the real build.
The frontend, backend or integration work you’ve handed us, in a repository you or your client own, or one we transfer to you at the end.
A staging site your project manager can review and share with the client on your schedule.
How to set it up, the environment variables, how to deploy it, which third-party accounts it uses, and anything it doesn’t do yet.
We suggest yours or your client’s from the first day, so there’s nothing to hand over at the end. If that isn’t possible, we agree how and when the transfer happens.
A clearly defined project usually suits a fixed quote. A backlog or a retainer you’ve sold to the client suits an estimate we review regularly. We’ll tell you which we think fits.
If the project already has a stack, we’ll work in it if we know it well. For new builds we usually suggest Next.js with TypeScript and managed hosting, and we’ll explain what that means for maintenance before you decide.
You send the scope, designs and anything the client has fixed. We ask what we need to estimate it.
You get a written estimate to price into your proposal.
We set up access and agree who does what.
We build in stages you can check and show your client.
Your team and the client review it. We fix anything that doesn’t match the scope.
We pass on the notes and access, and walk your team through it if you’d like.
Client IT teams, third-party platforms and late content often decide when a site can launch. We point these out when we estimate, so you can allow for them in your timeline.
The full process, from first message to handover, is on How we work.
A regional logistics group, via its digital agency
A purchasing portal for a logistics group across Singapore and Malaysia: one place to request, approve and track every purchase, connected to the finance system.
White-label work ranges from a few days on an integration to several months on an application, so we quote each project separately. You’ll see how the quote is made up before you add your margin.
After a first call, we send a written quote that says what’s included and what isn’t.
Yes. Your developers can review our code, and we can split the work by area or by feature, whichever suits the project.
We let you know as soon as we see it, estimate the change, and wait for your go-ahead before doing it. How you handle it with your client is up to you.
No. We work from your designs. If something in a design would be hard or expensive to build, we’ll tell you early.