Web Design in San Jose, CA
Sites and web applications built for a technical buyer: a real git repository from day one, staging environments, working CI, and code your own engineers could pick up and extend without translating it first. From $2,500, exact number after a free audit. On-site by arrangement, about two hours from our Sacramento office.
What it costs, by scope
Same three tiers as everywhere else, laid out as a table since that's usually the fastest way to compare options for a technical audience.
| Scope | Price | What's included |
|---|---|---|
| Business site | $2,500 to $6,000 | Design, build, forms, analytics, schema, a repo you can clone |
| Web app or portal with integrations | $6,000 to $15,000 | Logins, API integrations, staging environment, CI on merge |
| Custom build or platform | From $15,000 | Scoped and priced like the software project it is |
| Care after launch | $300 to $500 a month or $750 to $1,500 a month | Hosting and small edits, or a standing development retainer |
San Jose projects tend to have a technical stakeholder in the room from the first call, someone who wants to know the stack before they ask about the color palette. That conversation moves faster when the answer is a normal one: static site generator or a lightweight framework, deployed from a repo, nothing proprietary locking you in.
The table above is the same three-tier structure as our other pricing, business site, app or portal, custom build, but what moves a San Jose project between tiers is usually integration count rather than page count: how many APIs it talks to, whether it needs a real authentication system versus a simple password gate, and how much of the data model has to be designed. A five-page site with one contact form and a five-page site with a live pricing calculator pulling from your billing API are both "five pages," and only one of them costs $6,000. Full ranges on the pricing page, scope detail under websites and web apps.
Working with a technical buyer
When the person signing off can read a pull request, the process changes.
A lot of San Jose companies have an engineer, a technical co-founder, or a product manager who wants more than a finished screenshot. We built the process around that, and it is how our own site ships: deployed from a pinned commit behind more than 1,800 automated checks.
- A private repository exists from the first commit, and you get collaborator access if you want to watch commits land or leave a comment on a pull request.
- Every change goes through a staging deploy before it touches the live site, with basic checks running automatically on each push.
- The stack is documented in a plain README: how to run it locally, how deploys work, where the environment variables live, so a future engineer of yours isn't reverse-engineering our decisions.
- At handover, you get the repo, the hosting account and the CI configuration, not a zip file export from a page builder that only that page builder can open.
Software teams do this routinely, and many web vendors rarely offer it, since most build on a proprietary page builder specifically so you can't leave without them. We do the opposite on purpose: a technical buyer can verify the work in the repository itself, and a client who can eventually maintain the site themselves is a client who trusts the relationship enough to keep paying us for the parts they'd rather not do in-house.
A public site plus an internal tool, as one example
These two often get built together. The walkthrough below is an example workflow.
Say a San Jose hardware or B2B software company needs a public business site and, separately, a small internal dashboard, tracking device returns, or giving support staff a lookup tool against a database that currently lives in a spreadsheet three people edit.
Building both in the same engagement usually costs less than treating them as two separate vendors, because the authentication, hosting account and deployment pipeline get set up once and reused. The public site stays simple and fast; the internal tool gets a login wall and whatever access rules your team needs, admin versus read-only, for instance. Typical combined scope lands in the $8,000 to $18,000 range depending on how much logic the internal tool needs, and it ships on the same staging-and-handover process as everything else. See websites and web apps for the full range of what we build.
The internal tool doesn't need to be elaborate to be worth building. A lookup page against a database, a form that writes to a spreadsheet through an API instead of an inbox, a dashboard that shows the same three numbers a manager currently checks in four different tabs, all of these save more staff time than their build cost suggests. We scope these the same way as a public feature: a short spec, a fixed price, and a demo on staging before it goes live for your team.
Who we build for around San Jose
Hardware and semiconductor
Spec-heavy public pages, datasheets behind a gated form, and distributor login areas for companies selling to engineers.
B2B software and enterprise tools
Docs sites, pricing pages built for a procurement reviewer, and the customer dashboards that come with an early-stage SaaS product.
Professional and technical services
Sites for firms whose clients are themselves technical, patent attorneys, IP consultants, engineering recruiters, who need a site that reads as credible to that audience specifically.
Across all three, the same rule applies: no page exists because a template had a slot for it, and every form gets tested before launch. If you've inherited a site with no documentation and no access, the website takeover page is where to start.
We also see a fair number of companies that already have an in-house engineering team but no design capacity, or a designer who ships great mockups and no working front end. In both cases the project is narrower than a full build: we take the design or the existing codebase as a starting point and finish what's missing.
How we cover San Jose
IG Digital Lab works from 3550 Watt Ave, Suite 408, Sacramento, CA 95821, about two hours from San Jose. On-site visits for a kickoff or handover happen by arrangement; the build itself, including anything your engineers want to review along the way, runs remotely through the repository and a staging link. One address, one phone number, one listing. In San Jose, remote is how most engineering teams already work, so a project that lives in a shared repo and a Slack or email thread fits the way the company already operates.
Also in San Jose
Web design is one of several services we run for San Jose businesses.
Start with a free audit
A written review by email of scope, stack and a price range. Copy in whoever runs your engineering: questions about the repo, the deploy pipeline or data model get answered directly instead of relayed.
See full pricing Get the free auditFrequently asked questions
What San Jose technical leads and founders ask before signing.
Can our engineering team review the code during the build?
Yes. You get collaborator access to the repository from the first commit, not just at handover, so anyone on your team can watch commits land, leave comments, or flag something before it ships.
What does a site or app cost here?
Business sites run $2,500 to $6,000. A web app or portal with integrations and a staging pipeline runs $6,000 to $15,000. A custom build with real logic starts at $15,000, priced after a free audit.
Do you build the public site and an internal tool as one project?
Often, yes, and it's usually cheaper than hiring two vendors, since the hosting, auth and deployment pipeline get built once and shared. Combined scope typically lands between $8,000 and $18,000.
What CI or testing do you set up?
Basic checks run automatically on each push, a build check and linting at minimum, more if the project has logic worth unit testing. Every change deploys to staging first; nothing goes live without a review step.
How long from kickoff to launch?
Three to six weeks for a business site, six to twelve for a portal, tool, or a combined public site plus internal tool project, mostly gated by how quickly your side can review and approve staged changes.
Send us the stack. We'll read the repo.
A free written audit, emailed within two business days, and a price range.
Get the free auditOr call and text (916) 618-0502. English and Russian.
Tell us what's slowing you down.
You get a free written review by email within two business days.