Finally, weâre ready to share the Fibery Strategy for 2026, along with all the reasoning and plans behind it. Itâs a lengthy document, but we decided itâs worth sharing almost in full.
Check it out and add your comment, ask questions, or express any opinion. I will try to answer all the questions
Best,
Michael Dubakov, CEO
Hey Michael, Interesting read - thanks for sharing. Although I do see majority of people who chose Fibery were tech-savvy, Iâm not sure âCompanyâs OS for tech-savvy leadersâ is a âgoodâ positioning either. It sounds like a super niched down positioning - you tried that already with a product team focused positioning.
To me Fibery is not even a company OS. It is more like LEGO that you can build whatever you want with it. But I understand that âwhateverâ is nearly impossible to sell. Is LEGO for nerds btw? 
To me, Fibery is like Technic Lego, but where none of the instruction manuals (= templates) are likely to match exactly what you need. So you have to be able to look at all the available bricks/gears/axles/motors, see what other people have made, and then figure out how to build the thing you particularly need.
So yes, I would say that is âLego for ânerdsâ
Yes, you could say itâs a niche persona, as opposed to an industry niche. But itâs still a massive segment of the âCompany OSâ market.
The non-tech savvy leaders may well choose an alternative.
I can share that from the people who Iâve set up Fibery for as an implimentation partner, they were not tech savy leaders, but just didnt have a tool that could solve their problem as well as FIbery could. Since they werenât techy, they hired a partner. I think this could broaden the number of people Fibery can be relevant for.
Maybe in onboarding it can be a question, âHow technical are youâ then if the answer is that they are not technical, THEN hitting them up for a call / connecting to a partner. I see the value of not pushing for interaction for introverts, but assuming everyone is a technical introvert might lose a lot of leads who would find lots of value in Fibery otherwise. Donât get me wrong, I love the niche and see how Fibery would attract these people, but the product is also very valuable to companies who donât have tech savy leadership.
Thank you for sharing! 
The plans for 2026 look very promising and align perfectly with my expectations of âCompany OSâ
Youâre right that many people achieve great things with Fibery, without necessarily falling into the âtech savvy leaderâ niche, but as you say, it is often with the help of someone who is tech-savvy.
âCompany OS for tech savvy leaders, or for people who know (or can pay) someone to helpâ doesnât have quite the same ring!
I really admire you guys sending this publicly, and looking forward to seeing how the brand gets even crazier. (updated anxiety page�)
First of all, holy shit Q1 2026 is gonna be amazing. Really looking forward to better auto-linking (please add the full filter functions with groups, date comparisons, etc. Or just by using a formula. 
)
For Q2, I would like to just suggest one thing around the time tracking and workflow. I think making the workflow field more robust is valuable, but Iâm also weary of it being very different from the way ânormalâ Fibery works. Instead, I think it would nice to have âTemplate Fieldsâ where when someone presses âWorkflowâ it creates all the needed databases and automations needed for the workflow. Then it also shows indirectly teaches the Architect how things can be set up in Fibery. Same thing with Time Tracking, where the time tracking field is just a âButton Groupâ with linked âTime Logâ database. (only thing that would be missing is seeing the timer as the time passes)
Sad to see that âEntity as a dashboardâ hasnât made into next yearâs plan⌠yet.
And I think that if reports got a refreshed design, screenshots of dashboards would be a lot more âshareableâ.
Questions:
The visual rebranding: is it just about the website, or also the branding / style of the Fibery Platform?
Is the improved core performance also for bulk actions?
Hahah yeah of course. Attracting tech-savy people is the target, but just also being careful not to alienate those who are not. ie, provide support for those who are ânot tech-savy enoughâ, or utilise the partner program to support them.
Niching down is important, but also you donât want to leave money on the table for those who need an amazing tool like Fibery but are not technical.
visual rebranding should be for everything, starting from website and moving into the product eventually. We are on the early stage here, so will share more in January I hope.
Core performance is for everything, including batch updates in particular.
I fully agree here, we should balance it. In this scenario we consider partner as technical-savvy, but it is also important that this person will provide continuous support, since build-and-forget will be an eventual disaster.
You have no idea how seeing this kind of transparency manifest as well as many many of the words written in this document makes my heart soar for you, guys! The Who Are we? sectionâŚ
It makes me think that maybe there is still hope for decent human beings wanting to get some honest work done, lead by strong values first.
Thank you for who you are as a company and what you do as a product.
On a more constructive (and less emotional 
) feedback, there is maybe an area of growth that you have not yet identified (not surprisingly as it is probably quite niche): self-managed organisations and especially Holacracy/Sociocracy-run organizations. This ecosystem is very aligned on your core values and it is full of people that made their fight to harness complexity (not hiding from it) through collaboration and shared ownership, while still needing strong structure to navigate and operate. It echoes with how you describe your own product âcomplex and empowering, flexible but structuredââ. Holacracy if often presented as an Organization Operating System⌠Rings a bell? 
Our company follows the Holacracy Constitution and we implemented all of its aspects in Fibery. Frankly, itâs a match in heaven and I donât think anything come remotely close on the market. There are products available that will provide support for Holacracy (Glassfrog, Holaspirit, Nestr.io to name the most famous) but they usually stop there, all of them providing very basic project/action support. Holacracy is about implementing fluid organisations, always adapting and by implementing it in Fibery, you can make it work, fully integrated. Your tasks, projects are associated with Roles and Circles that will evolve when needed. But beyond that, every aspect of the organisation can be made compatible with Holacracy in a very intricate way: you need to define a process for spending requests involving different roles, you can do it explicitly; you need to create new entities to track you commitments to customer, they can still be assigned to holacracy roles; and the list goes on forever⌠Fibery is the perfect companion to implement anything that your organisation required, operationally or in terms of governance.
Itâs complex but fully structured, very liberating and incredibly powerful.
I donât know what it would mean for Fibery to go for this market. One caveat I see is that Iâm not sure of the average nerdiness in this community 
.
Maybe you donât need new features but just make yourself known in this community. Having a readily available Holacracy template could also help for sure. This is something Iâve been meaning to publish for a long time now, never finding the time to do it 
Anyway, if that is something you think might be of interest for you, Iâm happy to make myself available to discuss this further.
Iâve been rooting for the Fibery team for a long time.
Our brand and product is for people who need power, embrace complexity, understand abstractions, and share our culture. It is a simple, yet powerful idea for us.
This is one of the first times I would say my third-party opinion and the Fibery teams overlaps almost exactly.
Iâd love to see us host a Partner call where we collaborate on the future of Fibery and what role us partners can play in the 2026 strategy!
I loved this. It sounds like precisely the priorities I have. As someone who falls within the architect level, and who focuses a lot on maintaining simplicity for our users, Iâm excited about whatâs coming next year. Keep it up, guys!
Good that you share this - no build-and-forget, but keep in touch with clients as their loyal tech-savvy person, continuously improving their tooling. As Partners it is important to know what works for the Fibery team and the clients and and why. The transparent strategy already facilitates that - very cool. And conversations like these.
Hope we can keep this conversation going.
Edit: I see @helloitse wrote something similar - I agree Enoma! Letâs do that call!
Thank you for the transparency, Michael.
I am your nerd target customer and this month is my first as a paying customer.
Iâm coming from Airtable, SmartSuite and Supabase. Fibery felt a bit âSupabaseâ to me (good thing!), but with the front end I didnât have to bother trying to build. I liked that.
What has surprised me, given the nerd focus, is that we have an API that can be confusing, but we donât have really strong API docs. The nerd in me is re-building things Iâve built in Airtable, but the business owner in me is asking why Iâm bothering. Given that Iâm basically porting things Iâve already built, one would assume it would be easier. But itâs been tough without the quality documentation available in platforms like Supabase and Airtable.
Iâve started to think that maybe GraphQL is the preferred option for Fibery, given that it can apparently work with collection fields via named values rather than needing to know each optionâs ID. (I think your docs even mention that itâs preferred.)
I am surprised that, if youâre targeting us nerds:
Even ChatGPT has mentioned the Fibery API as being awkward and not well documented. (Though itâs been a big help to me in coming to terms with the way things are referenced.)
If there is one thing I think might be missing from your market strategy, it would be 100% follow-through on offering everything the ânerdâ needs to be successful. This is what Supabase did, and itâs paid off nicely for them.
I love what youâve built. I just wish it was a bit easier for me to wrap my arms around to build what I need on the backend. Iâll get there, but I donât yet feel empowered. And you know how we nerds love to feel empowered.
Happy holidays and happy new year to your entire team and all my fellow customers.