# Who is the primary audience for Baserow?

**URL:** https://community.baserow.io/t/who-is-the-primary-audience-for-baserow/12106
**Category:** Feedback
**Tags:** baserow
**Created:** [March 3, 2026, 9:17am UTC](https://community.baserow.io/t/who-is-the-primary-audience-for-baserow/12106 "2026-03-03T09:17:38Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![aaroncole](https://community.baserow.io/user_avatar/community.baserow.io/aaroncole/32/5085_2.png) [@aaroncole](https://community.baserow.io/u/aaroncole)
#### Post date: [March 3, 2026, 9:17am UTC](https://community.baserow.io/t/who-is-the-primary-audience-for-baserow/12106/1 "2026-03-03T09:17:38Z")

</div>

My concern is that you alienate the primary audience (non-coders) and dilute and confuse the product roadmap with features that require coding. If a Baserow product manager says, “our users really wish they could do X,” saying that it is possible “with a few lines of JS/CSS” is not the solution for this audience. Also, any solution that requires a paid account with external services completely destroys the economic argument for choosing this platform.

I am a huge fan of this product so far and want to be able to recommend that my employer make the purchase. I have taken the time to provide this feedback, not to complain, but in hopes that it will fall on receptive ears within the Baserow product team. Maybe make a non-coder persona and apply it in user testing every time you create a new feature. If a non-coder can’t use the feature, then it’s not ready for production.

I’ll be lurking in the forums and rooting for your success.

---

<div class="post-metadata">

### Author: ![olgatrykush](https://community.baserow.io/user_avatar/community.baserow.io/olgatrykush/32/219_2.png) [@olgatrykush](https://community.baserow.io/u/olgatrykush)
#### Post date: [March 3, 2026, 9:49am UTC](https://community.baserow.io/t/who-is-the-primary-audience-for-baserow/12106/2 "2026-03-03T09:49:56Z")

</div>

Hello @aaroncole 👋

Thanks a lot for taking the time to write this. You’re absolutely right — our focus is on non-technical users. When we suggest JS/CSS or other technical workarounds, it’s simply to offer a possible way to achieve something with the tools currently available. Our goal is to offer built-in features that are simple and easy to use for all types of users.

We also try to explain those workarounds clearly so non-technical users can follow along if they choose to.

Thanks again for the honest feedback — and for rooting for us. 🙌