Shipped work.

The workflow that wasn’t happening: PSBA wanted to feature its portfolio companies on the public site and publish press releases when companies hit milestones. The manual steps for either were enough that the team knew the work could be automated, but nobody had time to actually set up that automation. So the work just didn’t happen, either manually or automated. Portfolio companies sat unseen on the site. Wins went unannounced.

What I built: a secure-link portal that lets each portfolio company update its own profile on the public site. They edit without an account or password. Admin sees the change instantly. Logos normalize automatically. Part of a three-app suite built for PSBA: portfolio self-service, recording-to-press-release pipeline, financial automations.

The pattern translates to: any organization with a distributed roster that should be maintaining its own entries. Multi-location operators with managers updating store-level information. Family-owned businesses with department heads publishing project updates. Professional services firms with practice leads owning their own bios. Same pattern, bigger inputs.

The workflow that wasn’t happening: an AI fundraising platform needs to look like a real product before founders trust it with their pitch, and before partner institutions agree to put their name next to it. The team had the product, the credibility (Techstars alumni, $200M+ collectively raised), and a clear roadmap. What didn’t exist yet was a brand and a marketing site that matched the seriousness of what they’re building. An off-the-shelf template would have read like a side project.

What I built: a custom WebGL marketing site for Six Figures, the AI fundraising platform I co-founded with Arsh Haque. Liquid gradient backdrop, custom typography (Geist Sans plus Instrument Serif italic accents), engineered to be the front end the accelerator and investor tools plug into. When the product wires in, it inherits the same visual system rather than carrying a brochure site bolted to a separate app aesthetic.

The pattern translates to: any early-stage product where the founders need to look as credible as the product is. Solo founders pitching partner-institution deals. Two-founder companies where one owns design and the other owns engineering. SaaS startups that want a marketing site that won’t get torn down the day the app ships. Same pattern: the marketing site is the product’s design system, not a brochure on top of it.

The workflow that wasn’t happening: running a fractional consulting practice systematically without staff. CRM updates, meeting prep, opportunity tracking, draft writing, follow-up reminders. The operating work that traditionally requires a chief of staff or an admin team.

What I built: an 8-agent system with a dashboard. Each agent handles a function (research, drafts, meeting prep, opportunity sourcing, action items, reports). The dashboard surfaces what needs my attention. Everything else runs in the background.

The pattern translates to: any operator running a business at a scale that would normally need an ops team but doesn’t have one. Fractional executives. GMs at multi-location operators carrying coordination work across sites alone. Family-business operators carrying the chief-of-staff load themselves. Owner-operators at established businesses without internal admin capacity.

The workflow that wasn’t happening: every organization with a sprawling visual library has the same problem. The photos exist on phones, drives, clouds, hard drives. Putting them to use is a manual lift every time. Finding the right one means scrolling through thousands. Assessing what’s in them takes someone looking at each. Posting them anywhere means digging through the pile by hand.

What I built: a workflow app that turns a visual library into a managed, queryable corpus. Auto-tagging on every upload by what’s visible in the image. Vision-driven descriptions make the library searchable. The same vision pass drives assessments (pricing a service from what’s in the photo, condition assessments for inventory). From the same library, assets route to social posts in a click. First built for NailFile. The pattern translates immediately.

The pattern translates to: product manufacturers with sales and lifestyle photography across multiple SKUs and channels. Distributors with inventory photography that needs to be priceable and listable. Real estate firms with inspection and listing libraries. Multi-location service businesses where brand photography is owned by different operators. NailFile is the first vertical; the operating shape is the same in a 200-person regional company.

The workflow that wasn’t happening: On Purpose Oregon is a regional nonprofit supporting business as a force for good, run by a paid Executive Director and a working 16-person board. The board wanted a polished resource library on the public site for members, and a shared way to track sponsorship and partnership prospects with research on each one and a record of who’d been in contact. Neither existed. Neither was being managed. The ED was leading the org; the board was carrying the operational work between meetings. What didn’t exist was the tooling to make either project runnable without an ops coordinator the org doesn’t have.

What I built: two spreadsheet-backed systems. (1) A branded resource library on the public site that reads from a board-maintained Drive spreadsheet. The board adds links in the sheet; the site renders them as a polished, well-maintained library. (2) A sponsorship and partnership dashboard that auto-generates enriched research briefs on every prospect and includes a built-in CRM the whole board uses to track communications. The spreadsheets are the substrate. The systems are what got built on top.

The pattern translates to: any organization running real operational work but without the staff to hire ops coordinators. Working boards with paid leadership but no ops staff. Family-owned businesses where leadership runs strategy but no one runs operations. Small nonprofits with under-resourced development functions. Boutique partnerships with no BD lead. The spreadsheet is the substrate; the system is what gets built on top.

The workflow that wasn’t happening:a working 16-person board with a paid Executive Director running On Purpose Oregon, a regional nonprofit supporting business as a force for good. No grant management position. The board members each have full-time jobs elsewhere. There’s no slot for “scan grant databases weekly and write applications.” So grants the organization could be winning went unfound, and the ones the board did stumble across went unapplied to because nobody had time to draft the application.

What I built: a grant pipeline. It scans grant databases, RFP sources, and pitch competitions daily. It matches opportunities against the org’s profile. It drafts each application end to end, including attachments and required narratives, ready for the board to review and submit. It tracks deadlines and surfaces what needs the board’s attention this week.

The pattern translates to: any organization with no dedicated person scanning for opportunities. Mid-sized nonprofits with under-resourced development teams. Family-owned businesses pursuing strategic partnerships without a BD lead. Multi-disciplinary firms scanning RFP databases nobody has time to monitor. Boutique B2B sellers scanning for partnership and channel opportunities. Same shape, bigger inputs.