SmartDuke TechnologiesTalk to us
How we engage · 05 ways

Five ways to
ship an AI product.

Productized engagements with explicit scope and timelines. Pick the one that matches where you are. Every quote returns within 24 hours.

Compare engagements

Side by side.

Each engagement is a clear contract. Same disciplines applied; different scope and depth.

Attribute
01 / 05
Review
02 / 05
Discovery
03 / 05
Spark
04 / 05
Build
05 / 05
Embed
Timeline
1 week
1 week
2–3 weeks
8–12 weeks
Ongoing
Outcome
Audit + fix plan
Go / no-go
Working prototype
Shipped product
AI team on tap
Best for
Stalled or unclear existing project
Validating a new idea
De-risking a build
Shipping the real thing
Scaling what works
Eval suite
Gap analysis
Strategy only
Initial harness
Full coverage
Continuous
Observability
Reviewed
—
Light
Production
Production + alerting
Guardrails
Reviewed
Designed
Initial
Production
Iterating
Stakeholder demos
1 readout
1 readout
1 working demo
Weekly
Bi-weekly
From your workflow to the right engagement

Building an AI copilot into an existing product?

SmartDuke designs, engineers and operates custom AI products, including copilots and internal tools. Start with the engagement that matches the stage of your project.

01 / Discovery + Spark

Need to validate the use case?

Discovery covers use-case validation, system architecture, an evaluation strategy and a build estimate. If you need a working prototype before committing to production, Spark includes an evaluation harness and a go-to-production roadmap.

02 / Build

Ready to integrate a copilot into your SaaS product?

Our SaaS copilot approach combines tool-calling against the product API, retrieval from in-product context and structured outputs that the interface can render. Build is the production engagement, with evaluations, observability and guardrails.

Explore how we build copilots for SaaS
03 / Build + Embed

Planning for life after launch?

Build ends with documentation, evaluation suites, observability dashboards and an operating runbook. For ongoing engineering support, Embed includes evaluation and incident monitoring, continued capability development and quarterly architecture reviews.

Explore solutions for other industries
Always included · 06

What every engagement
ships with.

Whichever tier you pick, these are the disciplines we hold ourselves to. Not optional. Not extra cost.

01

Architecture documentation

Diagrams, decision logs, and a runbook your team can operate without us.

02

Eval scorecards

Frozen test sets, scoring rubrics, and pass/fail thresholds — handed over with the code.

03

Guardrail design

Input validation, output checks, escape hatches, and human handoff paths.

04

Security review

Auth, secrets, data classification, RBAC, and audit logs by default — not as add-ons.

05

Honest weekly writeups

What shipped, what didn't, what we learned, what's next. No corporate fluff.

06

Post-launch handoff

Code, infra, dashboards, and the full operating mental model — transferred to your team.

Principles · 04

How we build,
ship, and operate.

Four engineering disciplines we apply to every product we ship — independent of model, framework, or industry.

01 /04

Evals before launch.

Every AI product ships with a graded eval suite — unit tests on key behaviors, LLM-as-judge regression scoring, and human review samples. If it can't pass eval, it doesn't ship.

02 /04

Telemetry from day one.

Traces, latency budgets, token costs, error rates — wired up before the first user touches the product. You can't fix what you can't see.

03 /04

Guardrails as architecture.

Input validation, output verification, escape hatches, and human handoff paths designed in — not bolted on after the first incident.

04 /04

Boring stack on the edges.

Cutting-edge model in the middle. Reliable, well-understood infrastructure around it. Novelty where it earns its place; stability everywhere else.

Good things start with a conversation

What if we built
something that matters?

A new idea. An unsolved problem. A next chapter.
We’d love to hear what you have in mind.

Let’s start a conversation