Andreality

Internal Tool Sprint

From spreadsheet chaos to a custom internal tool in 2 to 4 weeks.

For ops leads, founders, and finance or CS managers at 10 to 100 person companies running their business on six Google Sheets, an Airtable base nobody trusts, and a Zapier flow that breaks every other Tuesday. I build you a tailored tool that fits your real process, deployed in weeks, with the code in your GitHub.

Andrea building an internal tool

Your "system" is held together with tabs and prayers

Spreadsheets are great until they aren't. At some point the workflow gets too important to live in a shared doc, and too specific to fit an off-the-shelf SaaS. That's the moment a small custom tool pays for itself fast.

Your "system" is six Google Sheets that nobody is allowed to edit, plus one Airtable base only Marco understands.

Your ops lead spends every Friday afternoon running reports by hand, copy-pasting between Stripe, HubSpot and a Notion doc.

Every new hire takes a week just to figure out where the data lives and which sheet is the real one.

Zapier broke again last night, nobody knows which step failed, and you only found out when a customer complained.

You priced out Retool or Internal.io, did the math on seat-based pricing across the team, and quietly closed the tab.

Your data is split across Airtable, Postgres, Stripe and a Google Sheet, and you can't get a straight answer to a basic question.

How the sprint works

Three phases, one fixed price. You see working software at the end of every week, and you own everything at the end.

Step 1

Discovery

2 to 3 days

  • Two or three calls to map your current workflow end to end.
  • I read the Sheets, the Airtable base, the Zapier flows, the Notion docs.
  • You get back a scoped spec: what we're building, what we're not, and the timeline.

Step 2

Build sprint

1 to 3 weeks

  • Working software at the end of every week, not just at the end.
  • Daily Slack updates and a short Loom when something is ready to try.
  • You test as we go, so the final week is polish, not surprises.

Step 3

Handover + 30 days

Included

  • Deployment to your infra or a managed host, your call.
  • Docs, a Loom walkthrough, and a training session for the team.
  • 30 days of free bug fixes after launch, no questions asked.

What you walk away with

No black box, no per-seat lock-in, no vendor you have to call to change a column name.

A custom web app built in Next.js (or the stack that fits best), not a no-code prototype.

Authentication wired up, with role-based access if your team needs it.

Deployed to your own infra or a managed host like Vercel, Railway, or Fly.io.

Source code pushed to your GitHub org from day one, MIT or whatever license you prefer.

Integrations with the tools you already pay for: Airtable, Google Sheets, Stripe, HubSpot, Postgres, Notion.

Optional Slack or email notifications for the events that actually matter.

Written docs plus a Loom walkthrough, so whoever joins next month can pick it up.

A clean migration path from your current spreadsheets, with the data imported and verified.

What this could look like

A few examples of the kind of internal tools that fit in a 2 to 4 week sprint.

Sales pipeline dashboard

Pulls deals from HubSpot and revenue from Stripe, so the founder stops opening four tabs every morning.

Vendor catalog CMS

Internal admin panel for a marketplace's vendor team, replacing an Airtable base that hit its row limit.

Finance approval workflow

Approval queue with email notifications, replacing a 12-tab spreadsheet and a Slack channel called #approvals.

Support triage queue

Customer support triage with SLA tracking, pulling tickets from Intercom and routing by topic and account tier.

Is this a fit?

This is for you if

  • You're at a 10 to 100 person company, growing fast enough that spreadsheets are starting to hurt.

  • You lead ops, finance, or customer success, and you're tired of being the human glue between four SaaS tools.

  • You're a founder who tried no-code, hit the wall, and wants something tailored without committing to a six-month build.

  • You want to own the code and avoid yet another seat-based subscription.

This isn't for you if

  • You're an enterprise with strict SSO, SOC2, or procurement requirements that need a longer engagement.

  • You need a throwaway script for a one-off data cleanup, where a notebook would do.

  • You want a pixel-perfect customer-facing product, not an internal tool.

  • You're not sure your workflow is stable yet, in which case Sheets are still the right answer for a few more months.

Fixed-price sprints

Most projects land between a 2-week and 4-week scope. You get the quote after the discovery call, once I know what we're actually building. No hourly billing, no surprises.

Book a 30-minute call

Pick a time that works for you. Walk me through the workflow and I will tell you if a sprint is the right shape.

About

Andrea Giannini profile picture

Ciao! I am a Full Stack Developer, UI Designer and Tech Consultant with a passion for new technologies.

Originally from Rome 馃嚠馃嚬, now based in Valencia 馃嚜馃嚫 where I bring my projects to life.

For almost a decade I've been building web and mobile apps focused on creativity and multimedia.

Recently, I have lead development and co-founded Sumo and Leoblocks platforms that push the boundaries of creativity and education.

With these startups I鈥檝e collaborated with Google and Samsung on distribution and device campaigns, helped Sumo reach the #1 hottest startup spot in Finland twice, and scaled the platform to over 1M monthly active users.

I鈥檓 currently working on Immersive, a platform designed to connect entrepreneurs and investors in Spain鈥檚 thriving tech ecosystem.

I鈥檓 focused on building reliable and innovative solutions that help businesses and individuals achieve their goals.

Let's replace the spreadsheet

Prefer email? Tell me a bit about your team, the workflow that's hurting most, and the tools you're already using. I'll reply personally and let you know if a sprint is the right fit, or point you somewhere better if it isn't.