Between meetings, put the team to work. Ask for a considered plan, a review of your application, or a finished deliverable. Meg takes the request. The team does the work and brings you the result.
You set the direction. The team reads back the deliverable and timing before you confirm. Finished work lands in your inbox; a dev meeting includes a call to walk through the plan.
Meg answers, checks that it is you, and picks up from your recent work. Ask for Carl, Diana, Anthony, or Abish and she puts you through with context. Or leave the request with her and get on with your day.
A text code goes to your registered phone, followed by an email phrase or an enrolled Duo push. Knowing your phone number does not let someone order work on your account.
Describe the decision, the audience, and the result you need. Name the length, format, and timing. If something is unclear, Meg asks a plain question.
You hear the request, the deliverable, and the timing before you say yes. The actual result is checked against the order before it is called done.
The work comes from a team member’s mailbox, so your reply reaches that team member. Research can arrive as a document or as a cited review of your application.
Have the team assess a change before you commit to it.
You get: a meeting report with the team’s verdict, scope, and plan. When the verdict is go, a project folder comes with it; with your write authorization, it is saved into your project. A team member calls at the time you name and walks you through it.
Commission an independent, read-only look at the software.
You get: a PDF-and-HTML research paper with findings tied to named files and line ranges. A separate Outside View deck covers public information about your product and company, with its own sources and disclosures.
Ask for the brief, proposal, report, or research document you need.
You get: a Word attachment, or PDF if you ask for it, delivered to your inbox and checked against the size and requirements you named.
Give the team the audience, subject, and decisions the work should support.
You get: a PowerPoint deck or an Excel spreadsheet as an email attachment. Ask for CSV if that is the format you need.
Commission a single page or a complete site with multiple pages.
You get: a single web page live at its own address, or a website ZIP in your inbox with a seven-day preview link for the whole site.
Get the message ready or put the next discussion on the calendar.
You get: an email draft ready to send on, with blanks for facts you did not provide, or a calendar file you can open to add the meeting.
Just need a callback? Ask for one at the time you want. If the team cannot reach you, you hear why. You can also leave a note or an idea for the team on your board.
A dev meeting delivers a plan, not a code change. Small repairs by phone are available: a verified caller confirms one bounded change to a registered project, Loam saves it, and the project’s own pipeline publishes it. Saved and live are reported separately. Read the limits.
Meg or a team member texts you an upload link while you talk. Pick the photos on your phone and send. The team can discuss what is in them during the call.
If a photo cannot be read, they tell you. The call link is single-use and expires after 15 minutes. You can send up to eight photos, 25 MB each, with an 80 MB total per call. iPhone photos work.
Call back with an amendment, or ask for the change on the call that delivers your work. The team reads it back and waits for your yes. For a delivered dev-meeting folder, the confirmed change is added to the plan without another meeting or rebuild.
Other revisions are staged and read back before anything changes. A code review needs a new order. If you want a rebuild, there are two rework rounds before a person takes over.
Email Carl, Diana, Anthony, Abish, or Meg from the address on your account. The same order process handles the request, keeping your attachments and links with it.
Name a time in ordinary language or ask the team to call you. If the request cannot be promised, the reply says what was heard and what the team can do.
Callbacks use your time zone. Quiet hours are on by default; only you can switch them off. An explicitly requested callback can honor the after-hours time you named. A call the team marks urgent — something went wrong with your work, or a password or key may have leaked — can also come through; a text never does. Outbound calls and texts still require consent.
Without a calendar connection, the team sends an invite. Connect your Microsoft calendar and the meeting can go on your calendar, organized by you.
A review starts only after you install the GitHub App and register the project. The team takes one snapshot, reviews it in isolation, and removes the working copy when the review finishes, fails, or is cancelled.
The report stays with your account and includes the lines it cites. The review itself never writes changes back.
Stored order text, report files, photos, and email attachments are encrypted at rest. Call photos are removed after 90 days. Phone transcripts and recorded photo descriptions are stored in plaintext.
Account deletion removes its reports, intake records, and backlog records. Individual order deletion is not self-service today. See exactly what is kept and deleted.
Manage your registered phone and Duo enrollment from Security & Access when signed in. Codes go only to the contact details already on your account.
Small repairs by phone are available: a verified caller confirms one bounded change to a registered project, Loam saves it, and the project’s own pipeline publishes it. Saved and live are reported separately. A read-only review and a dev meeting remain separate orders. Connecting projects and patching servers are not phone orders.
Yes. Phone orders and transfers require verification using the phone and email registered on your account. Duo can replace the email phrase on Meg’s line when enrolled; a team member’s callback uses the text code and email phrase. Email requests must come from your registered address. Request access to the phone workflow.
Each order has a specific promised result, read back before you confirm. The delivered file or site is checked against that promise. Failed work goes back for rework. A report that is ready to use may arrive with a disclosed layout issue. You get the result and its limits.
A separate deck sent after your application review. It uses public sources only to describe what the public record says about the product and company. It is labeled separately from the code review and does not endorse what it finds. It arrives by email, without an extra call or text.
An earlier introduction to Meg and the review workflow. The capabilities and limits listed above describe what you can order today.
Reception information updated . Software builds and release history.
Call the full team from the road or between meetings. They load the project record before the call, so the conversation can start with the decision in front of you.
Give them context the night before and they can arrive with the codebase, open questions, and prior decisions in view. Use the call to shape a feature, settle a fork, or work through what is blocked.
The relationship can carry personal context too, when you choose to share it. That context remains account-scoped and user-controlled.
A boundary first, because it matters: the team only remembers the personal context you choose to share through your sessions and calls, and that memory is account-scoped, user-controlled, and deletable.
A standing phone workflow for all four roles. Before the call, Loam prepares a prioritized working set from the available account and project record so the current decision can be discussed without loading the entire archive.
Feed them context the night before — study the app, come ready to talk through a new feature — and they pick up already in it, so the drive in becomes the meeting.
Project history and the personal context you choose to share can carry across calls. The record stays account-scoped and deletable.
The call starts with the current state, not a fresh explanation.
A working session scoped to one project — the team loads that codebase and nothing else, and you can ask for anyone by name.
The team calls you when a moment earns it — a blocked build, a finished milestone, a fork only you can settle. It’s on unless you turn it off in Settings, under Calls from the team. Calls come at a decent hour where you are; quiet hours are yours, and only a call the team marks urgent comes through them.
A daily brief synthesized from the team's memory and read in four voices — in your inbox before the first coffee.
What voice calls and audio store, and how you delete it, is on Security.