If the story was what the headline leads you to believe and you 10x'd someone's investment and they did you over, why wouldn't you see red and scuttle your product?
119 karma · joined January 29, 2019
If the story was what the headline leads you to believe and you 10x'd someone's investment and they did you over, why wouldn't you see red and scuttle your product?
it reminds me of the 2014 MBP which was a solid workhorse for at least 4 years.
To go back to the office 4+ times a week I'd be looking for something along the lines of: - 6-hour days without the pay cut - Significant pay rise - A product I'm genuinely passionate about
I just hate the commute and I do not believe anyone who had an inner city or outer to inner city commute who says they miss it. Sure it's fine some days when it's nice, everything is on time and it's not too busy, but most of the time it's grim.
I do think people romanticize what the office was like pre-covid. Only last week I was reminiscing on all the times we would complain about the lack of communication between teams, and that was when they were all sat in the same building.
I tried to get funding but never really got there and we've just managed to grind it out to a point where we have enough revenue to pay ourselves.
The flexible lifestyle is great, I play golf on Wednesdays and help out with childcare much more than I would have been able to with my previous jobs.
There is the looming threat that all our customers will leave us one day and I'll have to go back to a regular 9-5 job, but hey ho.
What problem are you solving: Team and office planning. Knowing when your colleagues are going to be working and where from. Then using this to provide insights into office usage. Use cases from our customers are much broader than what we had in mind.
Fully bootstrapped and past MVP doing, trying to justify bringing in a salesperson but given our background is in design and dev we're not sure where to start.
Currently we're at about 300 accounts we got there with a mixture of experimenting with Google/LinkedIn/Reddit ads, cold outreach and getting the product into as many marketplaces as we can.
We both work on it part-time with additional part-time help with customer queries. We've just got to the point where we can realistically move onto it full-time.
To start with, unless you already know people, raising money can be a full-time job in itself, everyone wants to offer advice and no one wants to cut a cheque.
I took a massively risk-averse approach instead of aiming for $1m ARR I started with building a self-sustaining app that pays the mortgage/rent, then all the bills, then matches your salary.
Smaller more achievable goals will stave off burnout because you won't feel like you're failing everyday you're not making $1m ARR.
I wouldn't be able to put a TV ad on SkySports with a song in the background of it without paying for usage.
The trend is going to continue over the coming years, especially with bigger offices that are paying millions each year.
If after a few years, it doesn't work, you go back to the market for more office space.
In the UK government orgs sold off their office space and turned to renting. Now the people renting the office space are annoyed that the demand is dropping. Poor them.
Everyone I ask for advice tells me to just start with 10 a week and see where it goes after a few months. So that's what I'm going to do.
Dev wise, going to try and develop plugins for more marketplaces as a means of improving the visibility of the product (confluence, slack, mattermost, etc).
So many people make it out to be remote v office and hybrid is the devil. I'm adamant that people want the flexibility to work how they see fit for the job at hand. Unfortunately, this doesn't typically align with all the other people in their division/team. Some will want to socialise in the office while others have commitments at home, some will want the focus they can only get in the office, while others want the focus they can only get at home. So you have a stalemate (or a planning problem).
I think Nick's right, in 10 years time it'll be a lot less controversial, there will be companies who are mainly remote, some who are main onsite and others that are both.
...and the groups of people who own office buildings who must be starting to sweat.
For me short lived branches that get merged into main dependant on passing tests and maybe a PR is by far the easiest, most reliable, and most common approach.
For many of the reasons listed, I do use TBD for my side projects. Push it to main, tested, built and deployed. Easy. :)
And on top of all that there's the strangest perception of value that can drastically change from person to person.
Companies could happily pay thousands for access to data for a single brands segmentation, then baulk at the idea of paying $7 per user for something like Slack that gets used many times a day by many people.
and step 4, i'd do the opposite. Choose a MASSIVE market. It'll be easier to get customers.
Out side of tech people who want to work in the office 5 days a week are in the minority along with people who want to work at home 5 days a week. The vast majority of people want the _flexability_ to decide when to go in. They'll go in for a change of scenery, to socialise with colleagues (not necessarily after work but idle chit chat in the office) or to informally speak to a few people.
Demanding and mandating people come back to the office is a real shitty move, and does nothing but cause stress and anxiety to everyone.
If you do go down the route of learning and upskilling in marketing. You'll probably find a solid startup idea along the way.
You could try something like a PM/BA role, orientated more around the user and stakeholder management. It's less tech focused and more time communicating with others but probably equally stressful.
I have a friend that bought a coffee shop in a midsize affluent town. Long days, always something going wrong beit staff sickness, stock shortage or maintenance. Kept it up for about 5 years, sold it on and went back into sales.
It only sounds like PMs have all the power because they put the tasks in the order that you work on them in, after haggling with all the other stakeholders.
I'd guess that the PM in the story trying to get some evidence to backup a decision/convince someone of something.
I've spent quite a while trying to formulate a response that covers everything but it's a deeply complex subject and touches on physical space constraints, employee development, cost (both to employee and employer), speed of decisions and response, and (all) employee wellbeing.
For every positive, there's a negative and if people aren't sure what to do I think they just default to what they're familiar with and knee-jerk back to what was the norm.
I think we're only getting started with remote working, my feeling is that there will always be office only companies (in the same way there's always been remote only companies). And the most common will be 'remote first' model where you can work where-ever you want but you're expected to attend certain meetings in the calendar in person.
Sales, sales, sales. It's all sales. And when there is feature development, it's because you've sold an improvements to a customer (but make sure they commit first).
The real difficulty is getting government or financial institutions to buy in, they have LONG approvals processes and require proof that certain security practices are being adhered to (ISO27001 helps but is costly).