What's the difference?
Both hold data. The difference is what happens around it: who changes it, what happens when it changes, and where it ends up.
| Spreadsheet | Work platform | |
|---|---|---|
| Several users | Copies and versions, or one shared file where everyone can change everything. | Each person sees and changes what their role allows. |
| History | Hard to see who changed which cell, when, and why. | Every change stays on the record, with a name and a time. |
| Deadlines | Someone has to remember to look. | Rules that run by themselves: when this happens, do that. |
| Work outside | Photos and notes arrive by message, and someone enters them later. | A mobile app on the same data, photos on the job, even with no signal. |
| Files and discussion | In folders and email, apart from the row they're about. | On the record they're about. |
| Reports | Built by hand, from a copy of the data. | From the live data, and sent on a schedule. |
| Getting started | You already have it and everyone knows it. | Takes setting up and getting used to. Your data comes in from the spreadsheet. |
When is it time to leave the spreadsheet?
If two or three of these sound familiar, the file already costs more than it seems.
- Several people open the same file
Every so often someone saves over someone else's change, or works on an old copy.
- You can't tell who changed what
A value changed and nobody remembers when or why.
- Deadlines live in someone's head
Permits, payments, renewals. When the person who remembers them is away, they slip.
- Photos arrive from somewhere else
They come in from the field by message, and someone matches them to the right row.
- The weekly report takes an afternoon
Someone copies, filters and sends it, every week.
- Several files that have to agree
Customers in one, projects in another, invoices in a third, linked by a code someone copies by hand.
When is a spreadsheet enough?
Not every file needs a platform. A spreadsheet is still the right tool when:
- One person updates it and everyone else just reads it.
- It's a calculation, not a workflow: a budget, a costing, a scenario.
- It's a one-off: a list for an event, a stock count.
- Nobody is waiting on anybody: there are no assignments, approvals or deadlines.
And after the move, spreadsheets don't leave your life: reports export to Excel whenever you need them.
How do you make the move?
Step by step, without stopping the work.
- 1Pick one file, not all of them
Start with the one that's opened most often and changed by the most people. Usually it's the list of projects or jobs.
- 2Set up your work
In Huskies you describe the company in plain words and Loki proposes records, fields, links and rules. You see them in a preview before they're applied. If you prefer, you do it yourself with the guided wizards, or we set it up for you.
- 3Bring the file in
Upload Excel, CSV or ODS and map each column to a field. Import shows which rows need a look before anything is saved, and you decide what happens to values that don't match.
- 4Move one job at a time
Statuses first, then reminders, then the weekly report. The file stays as it was, as a record of how you used to work.
- 5Retire the old file
Once the team works on the platform, keep the spreadsheet read-only. Two versions of the same data are worse than one.
Where does Huskies fit?
Huskies is a work platform made by Genuari: customers, projects, tasks, files, chat, reports and automations in one system, on web and mobile. It takes the shape of your company, with your own records, fields, statuses and rules, and your spreadsheet comes in instead of being thrown out.
See how it's set up for each use case