Airtable expertise. Business-first systems thinking.Nuanced
operations.
Sensible systems.
Every business has its “yes, but…” and “also…” moments. I’m Sally Ip. I help make sense of the details, exceptions, and moving parts—then design and build systems that make the work simpler without losing what matters.
Bring the context. You don’t need to arrive with the solution.
You bring the context.I bring the systems thinking.
01Understand what you’ve builtKeep what’s useful. Learn where the work gets difficult.
02Work through the tricky partsStructure, decisions, exceptions, and tools that need to talk.
03Build it. Explain it. Hand it over.A system your team can use—and understand.
Experienced help alongside you. Not a judgment on what you’ve built.
Understand → Design → Build → TeachDiscovery & architectureAudits & redesignImplementation & integrations
01 / Where I come in
There’s more than one
reason to bring me in.
You don’t need a technical specification. You need someone who understands the work and can help turn it into something usable.
THE INTERNAL BUILDERWhen building systems
isn’t your only job.
Perhaps you built the team’s Airtable setup alongside your day job. It’s useful—but the next workflow or integration calls for more time or technical depth than you have available.
I can work alongside you on the difficult parts, building on what you already know about the business.
Get experienced help alongside you ↗THE FOUNDERWhen an idea needs
a technical partner.
You may have a clear business goal, a list of possibilities, or just a process you’d like to improve. The technical solution doesn’t have to be worked out yet.
We can explore the options, prototype what matters, and build something you understand how to use.
Turn the backlog into a plan ↗THE GROWING STARTUPWhen the business
is changing shape.
A growing team may need more structure without committing to a large software stack. The useful question is what fits now—and what will still make sense later.
We can weigh the tradeoffs, keep the scope proportionate, and leave room for the system to evolve.
Build for the stage you’re at ↗ Selected work
Different operations.
The same search for clarity.
Selected project experience. Client names are withheld.
01 / Billing & collectionsFrom scattered account data
to prioritized work.
- The challenge
- Account information came from multiple enterprise systems. Matching records and understanding account-to-invoice relationships made collections work harder to navigate.
- What I built
- A staging base to unify Salesforce and Workday account data, plus AI-assisted account summaries, recommended collection actions, and daily task prioritization. I also redesigned interfaces to surface relevant context and actions.
- What changed
- Standardized account identities and contract-to-invoice relationships, with AI-prioritized work queues in place of manual review and automated prioritization to reduce investigation effort.
Airtable · Salesforce · Workday · Airtable AI
02 / Workforce schedulingFrom quarterly spreadsheets
to a shared scheduling system.
- The challenge
- Quarterly assessment scheduling needed to account for availability, assignments, travel, and administrative time—not simply put names on a calendar.
- What I built
- Structured Airtable workflows capturing availability and assignments, classifying visits by timing and assessment window, and generating templates for assigned visits.
- What changed
- Centralized quarter-wide schedules and availability, with visibility into workforce capacity and support for managers to locate and dispatch available assessors on demand.
Airtable · Interfaces · Automations
03 / Manufacturing & procurementFrom nested assemblies
to usable component quantities.
- The challenge
- Parts, assemblies, and bills of materials needed to be translated from a product lifecycle system into consolidated information for procurement.
- What I built
- A custom JavaScript function on AWS Lambda to process Arena PLM data, resolve obsolete part versions, flatten nested assemblies, recalculate quantities, and consolidate repeated components. The output flowed back into Airtable.
- What changed
- Automated procurement-ready component quantities and added a flattening capability unavailable in the source platform. Technical documentation supported maintainability and handoff.
Arena PLM · JavaScript · AWS Lambda · Airtable
Ways to work together
Understand it.
Improve it. Build what’s needed.
A review, a difficult workflow, or a new system can all be starting points. We’ll agree on the problem worth solving—not just the list of things to build.
01 / REVIEW WHAT YOU HAVEA clearer picture.
A sensible next step.
We look at how the system supports your actual work: what’s useful, what’s fragile, and what has become harder than it needs to be. You get priorities—not a reflex recommendation to start over.
Best for: “What should we improve first?”02 / SOLVE A BOTTLENECKGet the difficult
piece unstuck.
A complicated workflow, a data-model decision, or two tools that won’t cooperate. I help diagnose the problem, weigh the options, and implement the right fix with you.
Best for: “We’ve reached our limit here.”03 / BUILD THE NEXT STAGEFrom business idea
to working system.
We turn your business needs into a scoped plan, test a prototype, then build and connect the pieces. I’ll explain how it works so you can take ownership—not inherit a black box.
Best for: “We need someone to figure this out and build it.” Airtable, with more intention
Get more from
what you already use.
Airtable is a particular strength: relational architecture, interfaces, automation, scripting, and governance. Whether your base is an underused spreadsheet or a sprawling system nobody quite understands, I can help it do its job better. That doesn’t mean every business needs Airtable—or every Airtable needs rebuilding.
A working relationship, not a rescue missionYou know the business.
I’ll help shape the system.
Your knowledge of the day-to-day work is essential. I bring a fresh perspective, dedicated attention, and technical depth. Together, we can see the whole workflow—not just the next feature request.
- Keep what’s already working and understand why.
- Work through the exceptions before they become surprises.
- Give people the information they need at the moment they need it.
- Leave your team with clear ownership, documentation, and confidence.
03 / How we workWe’ll figure it out.
Then we’ll build it together.
01 / UNDERSTAND & QUESTIONModel the business.
Who needs to decide what? Where does the information come from? What happens in the weird cases? Sometimes those answers change what we thought we needed to build.
02 / PROTOTYPE & ITERATEMake it tangible.
We agree on scope and pricing, then test ideas with working prototypes. You see the tradeoffs, try the workflow, and help shape it—not wait for a mysterious finished system.
03 / EXPLAIN & HAND OVERBuild for whoever’s next.
Clear interfaces, sensible naming, documentation, and training matter. A good outcome is a team that understands its system and feels confident looking after it.
How I choose the toolsSometimes AI.
Sometimes a formula.
The useful question isn’t “can we automate this?” It’s “what should happen here—and who needs to decide?”
Keep the predictable predictable.
Use rules and automation for repeatable work. Use AI where interpretation adds something useful. Keep people involved where their judgment matters.
Build for your stage. Leave room to grow.
We’ll weigh subscription costs, build effort, and ongoing maintenance—not just features. Use existing software where it fits. Configure, connect, or build where it doesn’t. No-code when it helps; code when needed. No unnecessary migration.
04 / Meet Sally
I like complex problems.
Not complicated solutions.
The interesting part is figuring out why the work feels harder than it should.
I’m Sally, a Toronto-based systems consultant and builder. I move between understanding operations, designing the experience, and building the technical solution. You work directly with the person doing the thinking and the building.
I ask questions, show prototypes, and explain the choices. If a simpler process solves the problem, I’ll say so. My background includes workflow architecture, data modeling, integrations, and training teams to maintain their own systems. I work remotely with Canadian and US clients.
05 / Before we talkA few useful answers.
Can we start with just one part of the system?
Yes. A review or a specific bottleneck can be a useful starting point. We’ll identify dependencies, agree on a sensible scope, and decide whether more work is warranted.
Will you work with our internal builder?
Yes. They know the business and the reasoning behind the existing setup. I work alongside them, explain architectural choices, and help them maintain and develop the system with more confidence.
Do I need to know exactly what I want built?
No. Bring the problem, the current workflow, and what you’d like to improve. We can discuss whether there’s a good fit before deciding on next steps.
Do you only work with Airtable?
No. Airtable is a particular strength, but I also work with Asana, Smartsheet, Monday.com, and connected tools. I start with your business needs and recommend what fits—not a platform by default.
Can you help us get more from Airtable?
Yes. Many teams use Airtable without taking full advantage of its structure, interfaces, and automations. We can review your current setup and identify useful improvements before considering a rebuild.
Do you work with US clients?
Yes. I work remotely with Canadian and US clients. We’ll confirm meeting times, project expectations, and billing currency before starting.
How do you price your work?
Pricing depends on scope and complexity. I prefer clearly scoped project-based engagements; we’ll agree on the fee and what’s included before work begins.
A better workflow starts with a conversation.“It’s a bit complicated.”
Start there.
An Airtable base that needs its next chapter. A founder’s build backlog. A growing business held together by workarounds. Tell me what’s happening—we’ll figure out a sensible starting point.
Book a fit call ↗