Fixed-scope project
Three to six months. Scoped to a milestone with a definition of done, a price, and a date. We own delivery; you own decisions.
3–6 monthsProject price2 senior engineers
Services
Engineering, four shapes.
Same craft standard whether it’s a two-week sprint or a year-long modernisation. Pick the shape that fits the work — or talk to us and we’ll tell you which one does.
01 · Custom software
Web platforms and internal tools that hold up.
From customer-facing portals to operations dashboards to data tools nobody in the company can live without. We pick the same boring stack every time because boring stacks are the ones we can hand over in three years.
Brief us on a custom build→What we do
- Customer-facing web apps and portals
- Internal tools, admin panels, CRMs
- Data + analytics dashboards on top of your warehouse
- Backend services and APIs
- Auth, role-based access, audit trails
Who it’s for
- Funded startups past prototype, headed for production
- SMBs replacing brittle spreadsheets with real systems
- Product teams hiring senior contractors to ship a milestone
What you get
- Production-deployed system, monitored and documented
- Two-week iterations, demo every Friday
- Code, infra, and credentials transfer in full at handover
Sample stack
TypeScriptReactNext.jsNodePostgresRedistRPCHero UI Pro
02 · AI automation
LLM systems that survive contact with production.
There is a wide gap between an impressive demo and a system you can run for a year. We build for the second one — with eval harnesses, fallbacks, cost ceilings, and the kind of observability that makes the on-call rotation possible.
Brief us on an AI build→What we do
- Internal agents — research, drafting, triage, lookup
- Document ingestion + retrieval pipelines (RAG done right)
- Structured-output workflows: extract, classify, summarise at scale
- Evaluation harnesses + regression suites
- Cost + latency budgets enforced at the gateway
Who it’s for
- Operations teams replacing a manual workflow with an audited automation
- Product teams shipping AI features users actually rely on
- Founders past a prototype, before the first 1,000 paying users
What you get
- Versioned prompts and eval suites in source control
- Provider-agnostic gateway with fallback routing
- Spend dashboard + alerts before the surprise bill
- A runbook your on-call engineer can act on at 2am
Sample stack
AnthropicOpenAILangGraphPinecone / pgvectorTemporalModalBraintrustLangfuse
03 · SaaS development
Zero to product-market-fit, the unglamorous half done first.
Auth. Billing. Multi-tenant data. Audit logs. Email deliverability. Observability. The things that make a customer trust the product. We start there and let the differentiated work ride on top.
Brief us on a SaaS build→What we do
- Multi-tenant architecture from day one
- Auth + SSO (SAML, OIDC) wired to roles + scopes
- Stripe billing, plans, upgrades, prorations
- Transactional + marketing email pipeline
- Audit log, admin tools, customer support backplane
Who it’s for
- Pre-seed and seed founders past prototype, headed for revenue
- Vertical SaaS replacing an entrenched competitor
- Two-founder teams that need an engineering bench, not a hire
What you get
- Production SaaS your first 100 customers can use
- A foundation that scales to 10,000 without a rewrite
- Optional ongoing retainer — senior engineer on call
Sample stack
Next.jsPostgres + RLSStripeClerk / Auth.jsResendInngestVercel / FlyPostHog
04 · Enterprise modernisation
Legacy carried forward, not torn down.
The Big-Bang rewrite is the project that doesn’t finish. We migrate in tranches, behind a strangler-fig layer, with observability on both sides so you can compare old and new on the same request. The system stays alive the whole time.
Brief us on a modernisation→What we do
- Strangler-fig migration paths, incremental tranches
- API gateway + traffic-shadowing for old-vs-new validation
- Data migration with backfill + dual-write windows
- Observability + SLOs on every cut-over
- Documentation that survives the original engineer leaving
Who it’s for
- Established businesses with a system written before 2018
- Platform teams replacing a homegrown ERP/CRM
- CTOs who tried a rewrite once and need a smarter plan
What you get
- A migration plan that can be paused, resumed, and rolled back
- A working old system the entire time, until the new one fully owns the traffic
- A team that knows how to use it — runbooks, training, code review
Sample stack
Kong / EnvoyPostgres logical replicationDebeziumTemporalOpenTelemetryGrafanaTerraformGitHub Actions
Engagement
Three ways to start.
Each begins with discovery. None requires a commitment beyond the scope we’ve agreed in writing.
Ongoing retainer
Month-to-month. Two-week sprints, predictable capacity, the same engineers throughout. Cancel at the end of any month.
MonthlyCapped capacity1–4 senior engineers
Staff augmentation
A senior engineer embedded in your team for 3–12 months. They report to your lead, attend your standups, write code in your repo. We carry the management overhead.
3–12 monthsHourlyYour reporting line
Tech stack
The boring stack, by category.
Not a comprehensive list — a representative one. We pick from this set 95% of the time. The other 5% is for genuinely good reasons.
Frontend
TypeScriptReactNext.jsHero UI ProTailwindTanstack QueryZod
Backend
NodeGotRPCHonoPostgresRedisDrizzle
AI
AnthropicOpenAILangGraphpgvectorPineconeModalBraintrust
Infra
VercelFly.ioAWSTerraformCloudflareTemporalInngest
Observability
OpenTelemetryGrafanaSentryPostHogDatadog
Workflow
GitHubLinearFigmaNotionSlack
AI tools & automation
n8nMakeZapierClaude AIOpenAILangChainRelevance AIClaude CodeCursor
Process
Four steps. In more detail.
01 · DISCOVER · WEEK 1
Discover
Calls with stakeholders. Architecture review of what exists. A written scope doc, success metrics, build estimate, and risk list — yours to keep regardless.
02 · DESIGN · WEEK 2
Design
System diagram, data model, key screens, prototype where it earns its keep. Reviewed against the scope doc before any production code.
03 · BUILD · WEEKS 3–N
Build
Two-week sprints. Demo every other Friday. PR review on every line. Weekly written update; monthly invoice.
04 · SHIP · LAUNCH WEEK
Ship
Production deploy. Monitoring + alerts wired to your on-call. Runbooks, handover doc, two weeks of warranty support, code + infra + credentials transfer.
FAQ
Services questions.
A flat fee covering two weeks of work — calls, architecture review, written scope, and an estimate. You walk away with the deliverables regardless of whether we continue together. If you do, we credit it toward the build.
Want to work with us?
Send a brief. Discovery starts in two weeks, fixed cost, written scope and an estimate at the end.
Start a project→
Or email us: hello@codebyte.co.il