One focused workflow, a custom application, or a defined phase of a larger build. The proposal sets the scope; larger implementations are quoted individually.
Software, hosting, and AI usage fees are scoped separately. No ongoing retainer is required.
01 / Before the build
Start with a conversation.
Free / 30 minutes
Walk through the problem with Fahmid. Discuss what a useful result would look like and whether the studio is a good fit. No technical specification needed.
Maintenance and improvement work as your team learns from using the system. Agree on the capacity, responsibilities, and response expectations you need.
A sensible first commitment
Start focused. Leave room to grow.
A larger opportunity does not need to become one large bet. Start with a paid discovery phase or a focused implementation when that gives the project a clearer path.
The proposal defines what success means, what is included, what you need to provide, and what happens after launch. Additional work is agreed before it begins.
Workshops and implementation planning are also scoped individually.
The practical details
Before you commit.
What determines the project price?
The workflow’s complexity, the number of systems involved, the condition of the data, and the testing and handover needed. A focused first version can keep the initial commitment manageable without hiding important work.
What if the scope changes?
New requirements are discussed before extra work begins. Any effect on price, timing, or deliverables is agreed in a scope update. A fixed price applies to the agreed scope, not an unlimited backlog.
Are software and AI usage fees included?
Third-party subscriptions, hosting, and model usage are identified separately in the proposal. Wherever practical, you hold the accounts and pay those providers directly. Expected operating costs are discussed before you commit.
Can we start with discovery or a workshop?
Yes. If the implementation is too uncertain to price responsibly, a paid discovery phase or workshop can establish requirements, risks, and a practical plan before a larger build.
Do I need an ongoing retainer?
No. Ongoing support is optional and scoped to a real need. It might cover monitoring, maintenance, or an agreed amount of improvement work. Responsibilities and response expectations are written down; unlimited support is not implied.
Let’s understand the project first
What’s worth building?
Tell Fahmid where the friction is. Work out a sensible first step together.