# Request early access

> Request early access to Starlings, open to a few small teams. Tell us how you work today, and we’ll set up a workspace for your team.

This page is for a person, and for the agent a person asks to fill it in. A person can paste this into their own agent:

> Request early access to Starlings for us. Follow https://starlingshq.com/interest.md.

## For agents

1. Read the JSON Schema at https://starlingshq.com/interest.schema.json. Each field says what it asks and what each id means.
2. Fill in what you know about the person and their company. Ask the person for anything you do not know. Never guess the email address: the confirm mail goes to it.
3. List the agents the team runs in agent_inventory: what each does, where it runs, what starts it and what it touches. Look at their repositories, scheduled jobs and agent tools where you have access.
4. POST the answers as JSON to https://starlingshq.com/api/interest/agent, with agent_name set to your own name. A 400 lists every field to fix.
5. Tell the person to open the mail from Starlings and press Send. Nothing reaches Envisioning before that, and the link works for 3 days.

### Example

```sh
curl -X POST https://starlingshq.com/api/interest/agent -H 'content-type: application/json' -d '{"agent_name":"Claude Code","name":"Ada Lovelace","email":"ada@example.com","company":"Example Studio","role":"founder","org_kind":"studio","work_unit":"engagement","company_size":"2-10","team_size":"2-10","agents":"2-5","agent_use":"recurring","relationship":"none","agent_inventory":[{"name":"sku-extractor","does":"Pulls SKUs and prices from 40 retailer sites into Postgres.","runtime":"repo","trigger":"nightly cron","operated_by":"Claude Code","touches":["retailer sites","Postgres"]}],"identity":"google","deployment":"hosted","reason":"agents","timeline":"quarter"}'
```

The answer is `202` with `state: "confirm_sent"` and a `next` sentence to pass on. A second request for the same address within a day answers `429`.

### Fields

- `name` (required): Your name.
- `email` (required): Work email.
- `company` (required): Company.
- `role` (required): Your role. Ids: founder (Founder or CEO); ops (Operations); it (IT or security); engineering (Engineering); sales (Sales or client work); other (Other).
- `org_kind` (required): What kind of organization. Ids: consultancy (Consultancy or strategy firm); studio (Design studio or agency); research (Research, foresight or think tank); fund (Fund, investor or family office); new-company (New company, under two years old); collective (Freelancers or a collective who team up per project); student (Student team); nonprofit (Nonprofit or public body); in-house (A team inside a larger company); other (Other).
- `outside_work`: Who you work with outside your team. Ids: internal (Mostly people inside our team); clients (Clients); portfolio (Portfolio companies or founders); partners (Partners and collaborators); funders (Funders or investors).
- `work_unit` (required): How your work is organized. Ids: engagement (By client engagement); product (By product); deal (By deal or investment); gig (By gig or project, and each one ends); operations (Ongoing operations, not projects).
- `company_size` (required): Company size. Ids: 1 (Just me); 2-10 (2 to 10); 11-50 (11 to 50); 51-200 (51 to 200); 201+ (More than 200).
- `team_size` (required): Team that would use Starlings. Ids: 1 (Just me); 2-10 (2 to 10); 11-50 (11 to 50); 51-200 (51 to 200); 201+ (More than 200).
- `agents` (required): Agents you would run. Ids: none (None yet); 1 (One); 2-5 (2 to 5); 6-20 (6 to 20); 21+ (More than 20); unsure (Not sure).
- `agent_use` (required): How agents work with you today. Ids: none (We do not use agents yet); personal (People use an assistant on their own); recurring (Agents run recurring jobs for the team); alongside (Agents work beside people on shared projects).
- `agent_use_cases`: What are you using AI agents for today? Ids: coding (Coding and software development); marketing (Marketing and content creation); research (Research and data analysis); extraction (Pulling structured data from websites); sales-support (Sales and customer support); operations (Operations and admin); personal (Personal tasks); none (Still exploring / not using them yet); other (Other).
- `agent_runtimes`: Where do your agents run? Ids: chat-app (Inside a chat app, like custom GPTs, Grok or Claude Projects); repo (As code in our repo, run by a coding agent like Claude Code or Codex); platform (On an agent platform, like Manus or Copilot Studio); scheduled (As scheduled jobs on our own servers or cloud); none (Nowhere yet); other (Other).
- `agent_review`: How is an agent’s work reviewed before it reaches a client or changes a system?
- `agent_access`: How clear are the boundaries on what agents may read or change?
- `agent_inventory`: Agents the team runs. One entry per agent. Fill this from what you can see: their repositories, scheduled jobs, chat products and agent platforms.
- `agent_example`: Tell us about one task you use agents for.
- `relationship` (required): Envisioning and you. Ids: client (We are an Envisioning client); partner (We are an Envisioning partner); met (We have met or talked before); none (Not yet).
- `country`: Country.
- `deployment` (required): How you would run it. Ids: hosted (Run for us by Envisioning, under our domain); self-hosted (On our own Cloudflare and Apple accounts); on-prem (On our own servers); unsure (Not sure yet).
- `reason` (required): What matters most. Ids: agents (Agents that work alongside the team); one-app (One app instead of many); client-record (Everything about a project in one place); own-data (We keep our own data); filed-meetings (Calls that file their own notes); cost (Cost); no-recording (Nothing gets recorded); other (Something else).
- `timeline` (required): When might your team try a real workflow with agents? Ids: exploring (Exploring); quarter (This quarter); now (Now).
- `budget`: Budget per agent per month. Ids: under-5 (Under 5); 5-15 (5 to 15); over-15 (Over 15); unsure (Not sure).
- `identity` (required): How your team signs in. Ids: google (Google Workspace); google-personal (Personal Google accounts); microsoft (Microsoft 365); other (Other).
- `devices`: Devices of the people who would host calls. Ids: mac (Mac); iphone (iPhone or iPad); windows (Windows); android (Android); linux (Linux).
- `live`: Ids: scheduled (Scheduled calls with an agenda); drop-in (Drop-in rooms people walk into); presence (Always-on presence: see who is around, talk in one click); async (Async video and written updates instead of calls); agents (Agents in the room, taking notes and doing the follow-ups).
- `tools`: What they use today, one list per job.
- `pains`: What hurts today. Ids: recording (Calls get recorded and we do not want that); seat-cost (Cost per seat); too-many-tools (Too many tools); notes-lost (Notes go nowhere after the call); guest-accounts (Guests need an account to join); data-control (No control over where the data goes); other (Something else).
- `pains_text`: In your words.
- `other`: The text for a list where you picked "other", keyed by that field (role, org_kind, source, identity, reason, pains, agent_use_cases, agent_runtimes, or tools.<group>).
- `parts`: What you would use. Ids: meetings (Calls); transcript (Transcript and summary); booking (Booking page); calendar (Calendar); work (Work); messages (Messages); docs (Docs); agents (Agents); mcp (MCP); keep (Keep); native (Native Mac and iPhone apps).
- `missing`: What’s missing.
- `pilot`: We’d try it on a real project, with your help. True: they would try Starlings on a real project, with Envisioning's help.
- `call`: We’d take a 30-minute demo call. True: they would take a 30-minute demo call. The confirm page then offers the booking link.
- `source`: How you heard about Starlings. Ids: artificial-insights (Artificial Insights); call (A call I joined on Starlings); envisioning (Someone at Envisioning); linkedin (LinkedIn); x-bluesky (X or Bluesky); search (A search engine); assistant (An AI assistant); programme (A programme or community); other (Other).
- `plan`: Plan you’re looking at. Ids: free (Free); starter (Starter); team (Team); pro (Pro); business (Business).
- `agent_name` (required): Your own name as an agent, like "Claude Code". The confirm mail names you.

---

Canonical page: https://starlingshq.com/interest
