The Friday reconciliation
A job pulls the week’s Stripe payouts, checks them against the finance Google Sheet, and posts the mismatches to Slack.
USE CASES
Software too specific
for anyone to sell you.
Three people. Six weeks. One odd process. No vendor will ever build that, and your coding agent now can in an afternoon. Spryloom runs it behind email sign-in for the people you invite: a page for a report, a document or a prototype; a page that saves data for a checklist or a sign-off; an app when it needs rules, a schedule or email.
Operations
Every operations team has a process that exists nowhere else.
The office move
Forty desks, three movers and one weekend. Each desk gets a row, an owner and a tick when it is done.
Supplier sign-off, your seven steps
The seven steps only your company follows to approve a supplier, in the order you follow them.
SAY THIS TO YOUR AGENT
Build an app with a job that runs every Friday at 4: pull this week’s payouts from Stripe, compare them with the rows in our finance Google Sheet, list the mismatches, and post them to #finance in Slack. Publish it with Spryloom and invite the two people in finance ops.
Engineering
Someone does the same comparison by hand every week, and it is nobody’s job.
Shipped versus planned
Every Friday a job compares what merged in GitHub with what Linear said was planned, and emails six people the exceptions.
The migration dashboard
Three people follow the move from the old system to the new one. Your agent republishes it each morning, and it is deleted the day the migration ends.
The diagram for Thursday’s review
An interactive diagram your agent drew for one decision, opened by the eight people in the room.
SAY THIS TO YOUR AGENT
Build an app with a job that runs every Friday: list the pull requests merged in our GitHub repository this week, compare them with the issues planned for this cycle in Linear, and email the exceptions to the six people I invite. Publish it with Spryloom.
Data and analytics
One question deserves a proper answer, and a proper answer is not a screenshot.
The answer to one question
The CEO asked why churn rose in March. The analysis is a page five people can open, with the charts still interactive.
Launch-week numbers
A dashboard for one launch, republished each morning for ten days and then deleted.
The row-checking tool
Two analysts review the 400 rows the model was unsure about, one at a time, and their answers are saved.
SAY THIS TO YOUR AGENT
Write up the March churn analysis as one HTML page with the three charts and a plain summary at the top. Publish it with Spryloom, invited people only, and invite the five people on the leadership team.
Product and design
The prototype is needed for next week’s calls, and never again after that.
A prototype for five customer calls
The new onboarding flow as a clickable React prototype, shown in five calls next week.
Notes from twelve testers
Twelve testers leave notes on one build. Each note gets an owner and a status until the build ships.
The spec, read by Monday
A markdown file published in about three seconds, for the eight people who have to read it.
SAY THIS TO YOUR AGENT
Build a clickable prototype of the new onboarding flow in React, three screens, no backend. Publish it with Spryloom and invite the design team, so I can show it in customer calls next week.
Founders and leadership
The tools a founder needs are used by two people, so nobody makes them.
This quarter’s board update
Invite four board members by email. They sign in with a link, and nobody else can open it.
The fundraising tracker
Forty investors, who introduced each one, what they said last, and what you owe them next.
Offer approvals, your rule
Every offer needs a yes from both founders before it goes out. The app enforces exactly that.
SAY THIS TO YOUR AGENT
Make this quarter’s board update as one HTML page from these notes and numbers. Publish it with Spryloom, invited people only, and invite the four board members.
Sales and marketing
Your discount rules and your event follow-up are not a feature in anyone’s CRM.
The conference lead sorter
After the event, a job pulls the 300 new contacts from HubSpot and the team marks each one: call, email or drop.
Discounts, by your thresholds
Over 15% needs the regional lead. Over 30% needs finance. The app knows your thresholds and who to ask.
A battlecard for one deal
What to say against one competitor in one account, for the three people working the deal.
SAY THIS TO YOUR AGENT
Build an app that pulls the contacts added to HubSpot during last week’s conference and shows them as a list. Each of us marks a contact as call, email or drop, with a note. Publish it with Spryloom and invite the four people on the sales team.
Finance, HR and legal
The work is sensitive, the process is your own, and it runs twelve times a year.
Month-end close, your way
The 23 steps your finance team runs each month, with who did each one and when.
This year’s audit answers
Twelve owners each answer the questions assigned to them, in one place the auditor is invited to.
The policy sign-off
Every employee confirms they read the new policy, and HR sees who has not.
SAY THIS TO YOUR AGENT
Make a checklist for our month-end close with our 23 steps (I will paste them). Each step has an owner and is ticked off with who did it and when. Start a fresh list each month. Publish it with Spryloom for the finance team.
Agencies and consultants
Each client works differently, and the engagement ends in three months.
One client’s approval flow
This client needs legal, then brand, then the regional lead. Built for the engagement and removed after it.
The audit, as a live report
Invite two people at the client. They click a link to sign in, with nothing to install.
A status portal on your domain
Where each deliverable stands, for one client, at an address on your own domain.
SAY THIS TO YOUR AGENT
Build an approval app for one client: each deliverable goes to legal, then brand, then the regional lead, in that order, and each can approve or send it back with a note. Email the next approver when it is their turn. Publish it with Spryloom.
Agents and automation
An agent finishes the work at 3 a.m. and has nowhere to put it.
The overnight report
The agent finishes the analysis and publishes it itself. You wake up to a private link.
Only the exceptions, each morning
A job checks your Airtable base every morning and emails only the rows that broke a rule.
Decisions, posted where you work
When a blocker is resolved, the app posts the decision to #launch in Slack.
SAY THIS TO YOUR AGENT
When you finish the analysis, write the result as report.html and publish it with Spryloom, invited people only. Give me the link.
The familiar ones work too. They are a fine first app, and four are shown in detail below.
Request deskExpense approvalsTime-off requestsContent calendarEquipment logDeal desk
Yours is not on this list.
That is the point. Describe the odd thing your team does by hand, let your agent build it, and publish what it builds.
WHO IT IS FOR
Different work.
Different little apps.
Start with one process you already run. Spryloom gives each person a view shaped around that work.
All four examples use today’s building blocks: forms, lists, owners, comments, status, invited access, scheduled jobs, email, and approved outside services.Explore more examples →