![Mica H.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Mica H.")
MH

Mica H.

Head of Sales Support

Mid-Market (51-1000 emp.)

8/18/2026

"Powerful engine for complex operational systems — three years in, still finding new capabilities"

5/5

What do you like best about Lark?

We've built a full operating system across 3 business nature on Lark Base, covering project management, LMS, accounting tables, HR and etc.

For a no-code/low-code platform, it holds up impressively well under genuinely complex relational and financial logic. Table linking and formula flexibility let us model real structures that we can extract valuable info from.

The no-code layer means more of our team can build directly, which has meaningfully boosted efficiency and data visibility. CLI access opens the door to real automation beyond the UI, and there's a lot more depth in the platform than most people realize (ex we use Help Desk as our inner team support). Documentation is well done in English which matters a lot for our team.

I've used Lark for close to three years, and it keeps delivering surprises — witnessed the team continuously optimizes and rolls out new features, you can watch evolve over time. Compared to similar tools on the market, Lark is the one I'd genuinely recommend. Review collected by and hosted on G2.com.

What do you dislike about Lark?

Rather than dislike more like few of limitation of feature that I used often. Scale limitations are a consideration: each table caps at 20K records by default. There's an archive option that reportedly extends this up to 1M, but I haven't explored it myself yet and not sure what limitations come with it. Performance also noticeably degrades as record count and formula complexity grow, though there was a significant update last year that improved this.

Sync Base has its own limitations and is worth calling out separately: if a sync base disconnects, the downstream impact can be significant, especially once real data is flowing through it. Wouldn't recommend building core base data directly on top of a sync base.

Integration is another gap. Many common software tools in the market don't have native connectors to Lark, so we often have to route through third-party automation platforms just to bridge the two.

Pricing is also a pain point. Subscription tiering isn't very flexible. Review collected by and hosted on G2.com.

What problems is Lark solving and how is that benefiting you?

Lark Base is the backend for our entire operating system, replacing what would otherwise require custom software development. It handles complex logic while still being accessible enough for non-developers on our team to build and iterate directly. That gives us speed, better visibility into our data, and less dependency on engineering resources.

The newly rolled-out AI feature also opens up a lot of possibilities. A good example is drafting formulas with AI: it works well and enables teammates who have ideas but lack coding experience to turn those ideas into something real. Review collected by and hosted on G2.com.

Show More

Current UserValidated ReviewerSource: Organic

See what 175 reviewers think of Lark

4.5 out of 5 · Verified reviews from real users

[
Read all reviews
](https://www.g2.com/products/lark-lark/reviews)