# Work with Amidship | Product and engineering studio

> Canonical URL: https://amidship.com/work-with-us/
> Language: en-CA

Work with Amidship

# Start with the next important decision.

Amidship works best when the problem matters, the solution is not obvious yet, and product, architecture, and implementation need to stay connected. Start with a bounded engagement and expand only when the work justifies it.

Ways to start

## Bounded engagements with a concrete next step.

You do not need to commit to a transformation program to find out whether Amidship is useful. Start with the smallest engagement that resolves the next important decision.

- **Duration** 2 weeks

### AI Workflow Opportunity Sprint

For an important workflow that is still underspecified. We map the current process, decide where AI does and does not belong, surface delivery and governance risks, and leave you with a decision-ready architecture and scoped next step. **Deliverables** Workflow + opportunity map · architecture and control decisions · evaluation/risk plan · scoped build recommendation [Discuss a sprint](mailto:admin@amidship.com?subject=AI%20Workflow%20Opportunity%20Sprint)
- **Duration** Typically 6–12 weeks

### Governed AI Workflow Pilot

For one bounded workflow worth proving in real conditions. We design and build a working pilot around your systems, data, permissions, and human checkpoints, then evaluate it against explicit acceptance criteria. **Deliverables** Working pilot · integrations and controls · evaluation results · production/handoff recommendation [Discuss a pilot](mailto:admin@amidship.com?subject=Governed%20AI%20Workflow%20Pilot)
- **Duration** Typically 4–8 weeks

### Custom Product / Service Prototype

For a service or software problem where the product itself is still unclear. We move from discovery to a testable prototype, using the build to resolve product, workflow, and architecture decisions rather than hiding them in a deck. **Deliverables** Product definition · testable prototype · architecture decisions · user/acceptance feedback · build recommendation [Discuss a prototype](mailto:admin@amidship.com?subject=Custom%20Product%20%2F%20Service%20Prototype)
- **Duration** Typically 4–12 weeks; extend only by agreement

### Principal Architecture & Delivery Leadership

For a modernization or product initiative that needs senior technical direction before or alongside a larger team. Rida leads architecture, consequential decisions, and delivery review, with specialists added only where the scope benefits from them. **Deliverables** Architecture direction · decision records · delivery plan · technical reviews · handover [Discuss architecture leadership](mailto:admin@amidship.com?subject=Principal%20Architecture%20%26%20Delivery%20Leadership)

How delivery works

## Senior accountability without a handoff chain.

Principal-led does not mean undocumented dependence on one person. Decisions, architecture, code, risks, and next actions are recorded as the work proceeds, with client access to the relevant artifacts.

- ### Principal stays accountable

Rida leads discovery, architecture, consequential product and technical decisions, and final review.
- ### Specialists join by scope

When a problem needs additional expertise, specialists join with named responsibilities, access boundaries, and review paths rather than as an invisible bench.
- ### Continuity is planned

Planned absences and handover are handled in the engagement plan. If an unexpected absence would put delivery at risk, we pause or activate an agreed coverage plan instead of silently shifting the work to someone the client has never met.
- ### The work remains transferable

Decision records, repositories, architecture notes, test results, and handover material are kept current so the client is not dependent on one person’s memory.

Trust and governance

## The controls are part of the build.

Human accountability, bounded actions, least privilege, accessible interfaces, and clear records are treated as delivery requirements where they matter. We distinguish current practices from certifications we do not hold, and client-specific requirements are agreed before implementation.

[See government and trust approach](https://amidship.com/government/)

Start a conversation

## Have a problem that is difficult to get right?

Tell us what is happening, why it matters, and what makes it difficult. We can start there.

[Bring us the problem](mailto:admin@amidship.com?subject=A%20software%20problem%20to%20discuss)