Sundancæ Research Inc.
Pricing
Services

Engineering

Custom systems a business cannot buy off the shelf: internal tooling, data pipelines, pricing engines, inference services. Where the workload needs GPUs we run it on our own hardware, which is usually why the economics work.

Talk to engineeringRetainer pricing
Account snapshot
Across active engineering and advertising accounts
Live
11
Engineers deployed across active pods
$2.1M
Monthly ad spend under active management
12 days
Median time to first release
9.1%
Blended effective advertising fee
engineering: fortnightly release shipped to Core account
$14k/mo
Core floor - ~120 senior hours
2 weeks
Discovery sprint before anything ships
Fortnightly
Release cadence on Core and above
Yours
Source, infra and runbooks from day one
Retainer + compute

People are flat. GPUs are à la carte.

Core, Extended or Embedded on the left. GPU-hours on Sundancæ on the right. If the job runs on your cloud, that line is zero.

Retainer + compute on the same month
Retainer$14000
Compute$248
$14248 / mo
Compute is never buried in the retainer. If the job can run on your cloud instead, that line is zero. Three-month minimum, then 30 days’ notice.
In practice

How this actually runs

Engineering and advertising are two practices with one billing model: a flat monthly retainer, a small accountable team, and compute billed at the public rental rate. No templates, no percentage of spend, no subcontracted creative, no hourly change-order theatre.

Discovery is two weeks against your actual systems - APIs, warehouses, ad accounts, order backends - and ends with a scoped build plan and a number. If we are the wrong shop, that is the outcome. If we are not, Core is $14,000 a month (~120 senior hours), Extended $32,000 (a three-person pod), Embedded from $68,000 (operates as your department).

Engineering takes on software you cannot buy off the shelf: internal tooling, data pipelines, pricing engines, inference services, legacy migrations. Where the workload needs GPUs we run it on our fleet, which is usually why the unit economics work at all. Source, infra and runbooks are yours from day one. Deploy on Sundancæ or your cloud, written up front.

Advertising reads ad platforms, analytics and orders through APIs, trains a spend model on contribution margin, and buys media without taking a cut of spend. Creative stays in-house. Holdout tests validate incremental revenue. At $150k monthly spend, $14k is a 9.3% effective fee and falls as spend grows - the opposite incentive of a 12–15% shop.

Minimum term is three months, then thirty days’ notice. Compute used on our hardware still hits the rate card. If the job runs on your cloud, that line is zero. The client portal is where connected Meta and Google accounts show up once credentials are on file - that is a product of the advertising practice, not a separate SaaS.

How a build runs

Discovery, then a fixed monthly rate

Discovery

Two weeks against your systems, data and constraints. Ends with a scoped build plan and a number - not a slide deck.

Build

Fortnightly releases. You see working software. No hourly change orders; scope lives in the plan.

Operate

The team that built it can keep running it. Or we hand over. Deploy on Sundancæ or your cloud, your call, written up front.

Signal

Illustrative quarter · retainer vs compute on invoices

Retainer $k
Compute $k
32k24k16k8k0k
Jan
Feb
Mar
Apr
May
Jun
How to read it
Retainers are flat. Compute follows the job. We will not hide GPU hours inside the people line. Hover a point for the exact value. These series are illustrative of how the product behaves, not a live feed from your account.
One team does architecture, build and handover
Use cases: internal tooling, pipelines, pricing engines, inference services, legacy migrations
$14k buys roughly 120 senior hours - effective rate near $117/h
Compute consumed is billed at the public rental rate, not buried in the retainer
Questions

Straight answers

We say before it starts whether discovery is billed or credited against the first retainer month. It is two weeks against real systems, not workshops.
Related
If it is not off-the-shelf, we will look at it
Send the current stack and the constraint. Discovery is two weeks; after that you have a plan or a no.
Talk to engineeringRetainer pricing