Looker retainer
A part-time Looker engineer, without the hire.
Monthly retainer of three days of remote Looker engineering: LookML changes, new explores, review of your analysts' code, analyst training. Cancel any month, quote within 24 hours.
The problem
Between two projects, Looker needs upkeep: a new explore, a measure to fix, an analyst's change to review, a PDT that costs too much, a modelling question. Hiring for that makes no sense, waiting for the next project does not either. The retainer covers three days a month, taken in small slices, requested in writing and delivered as versioned code with an explanatory note. Unused days roll over one month. The first month always follows a LookML audit, so we start from a known base.
Who it is for
- Teams of 1 to 3 analysts on Looker without a dedicated Looker engineer
- Scale-ups between two data hires
- Companies that just finished an audit or a semantic layer and want to keep it alive
- Agencies operating Looker for their clients
What you receive
- Three days a month of LookML and dbt development, in half-day slices
- Review of all your team's LookML changes within two business days
- A monthly report: what shipped, performance, Looker-related BigQuery costs
- Written answers to modelling questions within one business day
- One asynchronous training session per quarter (video + exercises)
- Unused days roll over to the next month
Out of scope
- On-call, evening or weekend work
- Projects over three days (quoted separately)
- Looker instance administration
Prerequisites
- A LookML audit done in the last six months (by Neuravoid or a third party)
- Developer access to Looker and the repository
- A written channel (Slack, Teams or email) for requests
How it runs
01
Request
You describe the need in writing in the agreed channel.
02
Estimate
Answer within one business day: half-days needed, delivery date.
03
Delivery
Versioned code, explanatory note, video when the change deserves one.
04
Monthly review
Written report and next month's priorities.
StackLooker · LookML · dbt · BigQuery · GitHub · Slack
Frequently asked questions
Why a prior audit?
So that you do not pay three days a month of project discovery. The audit gives the map; the retainer maintains it.
What if we need more than three days?
One-off needs are quoted as a separate engagement. If it is regular, we move to a five-day-a-month plan, quoted in an addendum.
How does cancellation work?
In writing, before the end of the current month, no justification needed. Days rolled over from the previous month are delivered.
Do you work during our office hours?
Requests are handled asynchronously with written turnaround times. No meeting attendance is included; a monthly video check-in is offered.
Guides
9 min read · 5 September 2026
Looker Pricing in 2026: Editions, Licences, Real Cost
How Looker pricing works in 2026: Standard, Enterprise and Embed editions, Viewer to Developer licences, Looker Studio Pro, BigQuery costs, how not to overpay.
Read the guide →9 min read · 6 September 2026
Looker for e-commerce: margin, AOV, repeat, one revenue number
Ten e-commerce metrics defined once in dbt and exposed in Looker: net revenue, margin, AOV, repeat rate, returns, grain trap. With a public reference repo.
Read the guide →10 min read · 6 September 2026
Looker for fintech: TPV, chargebacks, churn, loan book
Settled vs attempted TPV, take rate, chargeback ratios against Visa and Mastercard thresholds, customer-month churn, point-in-time loan book, SCD2. Public repo.
Read the guide →Describe your context
Three lines are enough: your stack, what is broken, the deadline. Written answer within one business day, call optional.
Request a quote