Hiring a web development studio is weird. You're asking someone to build something you can't fully specify, on a timeline you can't fully predict, for a budget that could be anywhere from $5,000 to $500,000 depending on what the thing is.
Most agencies make this worse with vague "let's hop on a call" funnels that don't answer your basic questions. Jamii Technology tries to do the opposite — tell you up front what working with us actually looks like.
Here's the full playbook.
Step 1: The first email
You send an email to contact@jamiitech.com or fill out the form on /contact. Include:
- What you're trying to build (one paragraph is fine)
- Your rough budget range, if you know it
- Your target launch window, if you have one
- Links to anything you like or don't like design-wise
You will hear back within 24 hours — usually from me directly. If the project isn't a fit, I'll say so and recommend someone else. If it is a fit, we'll schedule a 30-minute call.
Step 2: The discovery call
The goal of this call is to figure out:
- What the riskiest part of this project is (technical, scope, timeline, or budget)
- Whether we're the right team to own that risk
- Roughly what the engagement would look like
I'll ask you questions like "what happens if we launch and nobody uses it?" and "what's a hard no on scope?" Those questions are meant to pressure-test the project, not to talk you out of it.
At the end of the call, one of three things happens:
- Yes, let's do it. I'll send you a proposal within 3 business days.
- Maybe, let's do a paid 2-week scoping engagement. Used when the project is complex enough that writing a fixed-price proposal would be irresponsible. Scoping engagement is ~$5K, output is a detailed spec you can take to any agency.
- No. We'll tell you why and recommend someone else. Happens about 30% of the time.
Step 3: The proposal
Our proposals include:
- Scope (what we're building, in plain English)
- Timeline (week-by-week milestones)
- Budget (fixed price, in ranges for sub-components)
- Team (who from Jamii Technology is on this project, and how much of their time)
- Exclusions (what we are not doing — this is the most important section)
Everything is negotiable. If the price is wrong for your budget, we'll talk about cutting scope to match — not cutting corners on delivery quality.
Step 4: The build
Once you sign:
- Week 1: Kickoff, design review, repo setup, staging environment
- Weeks 2-N: Ship weekly. You get a staging URL. You see progress in real time.
- Every Friday: 30-minute status call. 15 minutes what we did, 15 minutes what we need from you.
- Launch week: Production deploy, DNS cutover, monitoring setup, handoff documentation.
No endless status meetings. No Slack channels that you have to babysit. If something is wrong, you'll hear from me, not a ticket in your inbox.
Step 5: Post-launch
Standard post-launch includes 30 days of bug fixes at no charge. After that, you have two options:
- Retainer: Monthly retainer (~$2K-$8K depending on site) for ongoing updates, content changes, analytics, and monitoring.
- Project-by-project: No retainer, just hire us when you have a new feature or a bug.
Most clients go with the retainer because the ongoing cost of neglecting a website is higher than the retainer price. But it's your call.
Pricing ranges (actual numbers)
We don't publish fixed prices because the range is too wide. But broad ranges:
- Landing page + basic content management: $8K-$15K
- Marketing site (5-10 pages, blog, CMS): $15K-$40K
- Web application (auth, user state, payments): $40K-$150K
- Full product 0-to-1: $80K-$300K over 3-6 months
- Ongoing retainer: $2K-$8K/month
If your project is under $5K, we're probably not the right fit — we'd recommend a freelancer. If your project is over $500K, we're also probably not the right fit — that's a team of 10+ engineers, not a studio.
What we're good at
- Custom websites and web apps for Bay Area startups, nonprofits, and enterprises
- React + TypeScript + Supabase + Vercel stack
- Founder-led product work, especially 0-to-1
- Headless CMS work (Sanity, Payload, Supabase)
- Performance optimization and SEO
What we're not good at
- Native mobile apps (we can do React Native for web-parity apps, but not ground-up iOS/Android)
- Enterprise salesforce/oracle integrations
- WordPress (we don't work in WordPress)
- Designs that aren't directional — we need either a brand or a strong direction to do our best work
Ready to talk?
Email contact@jamiitech.com or start a project here.
— Danny McLane, Founder, Jamii Technology
