A written scope before any work starts.
Every Giant Entity project runs the same way, whichever kind of work you need. It starts with a call with the person who leads that work. After the call you get a written scope with a fixed price, and nothing starts until you agree it. While the work is under way you see real progress every week, and at the end every file we made is yours.
What you can hold us to.
A written scope before any work starts.
We write down what we will make, who will make it and what you will have at the end, and you agree it before we begin. You can check both the work and the people before you say yes.
A weekly look at real progress.
Each week you see the work itself, as far as it has got: the actual designs and pages, the records in the database, or the asset in your build. Nothing at the end comes as a surprise.
Every file we make is yours.
Source and design files come with the finished work, from the logo's source files to the site's code, the database, the automations and the written instructions. Nothing is locked to us.
A monthly arrangement only when there is something to keep.
Nothing runs monthly until something is live and needs looking after. Then it is a set block of named work each month, and you can see what it covers before you agree.
How we use AI.
We use AI tools where they are reliable, people decide and check everything, and your data stays out of them unless you agree.
From the first call to the first day of work.
Book a call.
Booking takes three short steps: what you need, anything we should know, and your details with two times that suit. You get a call brief to keep, and it shows who will be on the call. We reply by email to arrange it.
The call.
You talk to the lead for that kind of work. We ask about the situation in your words, what exists today, what has to be true and by when, who decides, and anything that is fixed, such as your tools, your data, your engine version or a launch date. We do not quote a price on the call. We tell you when the written scope will arrive.
The written scope.
One or two pages: what we will make and what is left out, who will make it, what you will have at the end, the milestones, the fixed price and how it is paid, and what we need from you.
If the work is not clear yet.
Sometimes the honest answer is that nobody can scope it until someone has looked properly. Then we suggest a first step that is scoped and priced on its own, such as a site and search audit or a process map, and you decide what comes next with the findings in hand.
If we are not the right fit.
We say so early: if the work sits outside what we do, or we cannot give it the days it needs. Where we can, we suggest who to ask instead.
The shapes work takes.
Each one starts with a written scope.
A sprint
A short, fixed piece of work over a few weeks, with one named outcome. A site and search audit or a process map fits this shape, and so can a brand identity.
A project
Larger work in milestones against a written scope, such as a brand and a website together, or a database with the automations around it. You own everything at the end.
Co-development days
For game studios already in production: we join your team for a block of days each month, inside your own pipeline. The days are agreed in writing before work starts. More on Co-development days.
Keep
Once something is live, a monthly block of named work to look after it. Offered only when there is something to keep.
What helps us help you.
You do not need a brief. A sketch, a spreadsheet, a game in production or just a launch date is enough to start. These make the call more useful:
- For brand and websites: your current site or brand files, a few sites you like, and any date you are working to.
- For workflow and automation: the tools you use now, and the task your team repeats most. Describe your data rather than sharing it.
- For product visuals: CAD files or product photos, your colourways and your launch date.
- For game work: your Unreal version, how you handle source control, a style reference, and when you need us to start.
More on Why one studio, or read the Questions we are asked before a call and Giant Entity at a glance.