Dedicated developers

Your team. More engineering capacity.

Add engineers to your existing team. You direct the work; Salt supports the people and continuity of the engagement.

Managed development teams

A good fit when you need a coordinated team to deliver a product or workstream. The proposal defines development, testing, technical leadership, and reporting responsibilities.


Explore managed teams

Dedicated developers

A good fit when you already have delivery leadership and need specific engineering skills. Your team manages priorities and day-to-day work.


Explore dedicated developers

Project-based development

A good fit when the deliverable can be defined clearly. We agree on scope, assumptions, milestones, and a process for handling changes.

Assessment or pilot

A focused starting engagement can help clarify an existing system or test how we work together. Scope and success criteria are agreed before it starts.

Your delivery process stays yours.

Dedicated engineers work within your team’s priorities and practices. For Salt-managed delivery, explore SPARK to understand how we structure scope, review, release, and improvement.

How Salt structures delivery

Working with US companies

Your business in the US.
Engineering with Salt in Pune.

Choose who will lead delivery, then define the working arrangements. The operating model below separates your responsibilities from Salt’s; commercial terms are specific to your engagement.

ResponsibilityDedicated engineersManaged development team
Business prioritiesYour product owner sets priorities and accepts business outcomes.Your product owner sets priorities and accepts business outcomes.
Day-to-day deliveryYour team directs the engineer’s tasks, reviews, and delivery process.Salt coordinates the agreed workstream and reports progress to your decision owner.
Technical leadership & QAYour team supplies leadership and testing unless separately included.The proposal identifies the leadership and testing included in Salt’s scope.
Changes and blockersYour delivery lead manages prioritization and dependencies.Salt raises delivery blockers and scope changes for your decision.

Contracting and billing

Your proposal and agreement need to identify the legal contracting entity, scope, billing currency, payment schedule, and change process. US presence does not by itself determine the entity signing your contract.

Communication overlap

Identify your time zone, essential live meetings, delivery contacts, and escalation owner. Record the overlap window in both US local time and India time, including how daylight-saving changes are handled. Full US-day or 24/7 coverage is not a default commitment.

Source code and access

Separate repository access from legal ownership. Specify who administers the repository and deployment accounts, what code and assets are delivered, any pre-existing or third-party components, and the applicable IP terms.

Progress and acceptance

Define a review cadence, a shared view of work and blockers, and the person authorized to accept a deliverable. For each release, identify the acceptance criteria, known limitations, and unresolved issues.

Handover

List the handover deliverables: source access, setup and deployment instructions, environment requirements, outstanding issues, and a walkthrough. Identify the people receiving access and the system owner after delivery.

Support after delivery

Distinguish defect correction from new features and ongoing operations. Specify the support period, coverage hours, severity definitions, response targets, and escalation route. An ongoing support arrangement must be included explicitly.

Before we begin.

We agree on communication hours, access to your systems, source-code ownership, confidentiality, replacement arrangements, and support responsibilities. Exact terms belong in your proposal and contract.

Compare developers and managed teams

A good place to start

Tell us what you want to build.

Share the challenge. We'll help you work out the next step.

Let's talk about your project