Automatically translated.View original post

Figma just updated the plan. Do we have to pay more?

So which plan is for our team?

.

Let's find out with the live session "Right Figma Plan, Right Team: Which Figma Tier is right for your team? Let's find out together" of Friends of Figma, Bangkok with Mr. Folk. Tanon Techanithijinda Design Advocate of Tangunsoft is the one and only Figma plan sales dealer in Thailand.

.

⭐ Why does Figma need a plan? Then what's the seat?

What plan do we usually buy from the number of designers? What kind of plan or seat would we buy?

Many organizations mistake buying a designer for a seat and a gap. Excess costs, such as designer 3 dev 4 po 10 buying a full seat, may not be appropriate for each person.

Figma is a platform, creating UI / UX and developing features, adding more and more and having their own application objectives, such as Dev Mode, FigJam, Figma Slides, answering questions with others on the team.

In addition to being a designer tool, it is also a collabration tool. It is done from start to finish to create 1 product. Use Figma according to objectives and responsivity.

- Designer: Used to make UI, prototype, components and so on.

- Developer: Come in to inspect the home page as well as pass the work from designer to developer seamlessly and use MCP to gen code.

- Product / PM: align scope, review, comment, share to other stakeholders

- Stakeholder: Come in, review and stay in the whole process.

Our choice of plan may not solve the problem now. Purchase depends on the purpose of use and the page focused on the purchase by seat, such as Full Seat, Dev Seat, Collab Seat, suitable for PO, not to edit the UI, edit the code, just Figma Slides, FigJam.

.

⭐ Understand the plans and seats.

📝 Plan is the ability level of the team / organization and the overall management model. There are 4 plans.

- Starter: Fits people who are just starting to use it. Use it alone. Share it visually and concept. It's the only plan for free. - If personal use is not addicted to anything, the freelance has precautions.

- Professional: Start working with more teams, develop into products and teams - 1 team, not many people, or outsource work for others

- Organization: There is a need for more teams and more use with other teams in the organization itself, manage the design system and admin. There are also many teams. Do not want other teams to see our team and manage the library from the middle. Separate the team by product.

- Enterprise: For big organizations that need more security, there are a lot of backends, setting permission and domain restrictions, such as banks.

🪑 Seat is the permission for each user to be responsible. There are 4 types:

- Full Seat: Reach all Figma products in design with Figma Design, Figma Make, Figma Draw, Figma Sites, Dev Mode, FigJam, Figma Slides, Figma Buzz

- Dev Seat: Dev Mode, Figma Slides, FigJam left on the job plan.

- Collab Seat: Fits the squat product maker. It is responsible for planing documents. Design flow left Figma Slides, FigJam.

- View: You can see it, but you can't edit anything. Comment is only free.

P.S. Figma Sites and Figma Buzz are beta, as you read on the web.

.

⭐ price?

Brother Banks says it's at least cheaper than Adobe. 🤣

On the web page, we have to choose a plan and then take care of the seat.

Which plan organization and enterprise only collect annually

So the price paid will be based on the number of seats used in each plan.

- Professional: Full seats $16 / month, Dev seats $12 / month, Collab seats $3 / month

- Organization: Full seat $55 / month, Dev seat $25 / month, Collab seat $5 / month

- Enterprise: Full seat $90 / month, Dev seat $35 / month, Collab seat $5 / month

There is also AI credit. Each seat in each plan will be different. It works well to a certain extent. But before it was limited enough, there was no money to use for free. In the last month, it was just overused to buy more. Credit is out of purchase per seat. Or it is an additional credit as a pool of shared teams.

The add-on model of organized with enterprise is a subscription to pay-as-you-go that we can turn off by default and limit the monthly limit.

And good news, starter, try MCP support on the outside, in case you want to try something.

.

❓ okay. The plan's in use. Okay with us. Okay with the team?

Free starter, the rest is not free, depending on the seat we buy, and who does each plan suit?

- freelance. Customers need a lot of screens and no complexity. Start can also be ok. But if you do it more seriously, recommend as a professional because the features are less restricted.

- So, which moments have to go professional? Hands-off is more difficult because of limited credit and a lot of effort to transfer tasks, including file management. Files will be in the draft. If the pro has a team, has a project to manage files in each folder, or part 1 file can't start. There must be several file design, including a design system to manage the library.

- So, which moment from professional to organized? limit feature is not enough and manage more of our files, teams, libraries.

- Organized, started with multiple teams, have documents, reduce consistency. If the organization has central management, is done, and automatically set up, such as resigns, is unsigned, new arrivals are automatically granted permission by email domain.

- Managing professional files build a project-based team and contain files. The enterprise has folders and file breaks branches.

- And can crack branches and merge back. There is a review before merge back handle all which must be an organization or more.

- There are many teams in the organization. There are many folders in each team. There are many files in the folder. There are many branches in each file.

- Library access control for organizations

All will be about this, right?

# Includes IT matters # Share IT Trick # Post receiving summer # Drug sign with lemon8 # Lemon 8 Howtoo

4/19 Edited to

... Read moreถ้าใครเสิร์ชชื่อ “Tanon Techanithijinda” แล้วอยากรู้ว่าเกี่ยวกับอะไรกับ Figma—จากที่ตามไลฟ์/สรุปงานของ Friends of Figma Bangkok มา คุณโฟล์ค Tanon Techanithijinda เป็นสาย Design Advocate ที่เล่าเรื่องการเลือก Figma Plan และการจัด “Seat” ให้เหมาะกับบทบาทในทีมแบบเข้าใจง่ายมาก ๆ (ไม่ใช่แค่พูดราคา แต่ชี้ให้เห็นกับดักที่หลายทีมเผลอซื้อแพงเกินจำเป็น) สิ่งที่ผมชอบคือการย้ำว่า “Plan” กับ “Seat” คนละเรื่องกัน: Plan คือระดับความสามารถ/การจัดการของทีม (Starter/Professional/Organization/Enterprise) แต่ Seat คือสิทธิ์ของผู้ใช้แต่ละคน (Full/Dev/Collab/View) ซึ่งพอ Figma มีของอย่าง Dev Mode, FigJam, Figma Slides และมี AI credits เข้ามา ยิ่งทำให้การแจก seat ตาม “ตำแหน่งงาน” สำคัญกว่าแจกตาม “ใครเข้ามาใช้งานบ้างก็ให้ Full หมด” ทริคที่เอาไปใช้ได้จริง (อิงจากแนวคิดที่คุณโฟล์คอธิบาย) คือเริ่มจากไล่บทบาทในทีมก่อน แล้วค่อยเลือก seat: - Designer ที่ต้องสร้าง UI/Prototype/Component จริง ๆ ค่อยเป็น Full seat - Developer ที่เข้ามา inspect/ดู spec/ใช้ Dev Mode เป็นหลัก มักพอที่ Dev seat - PO/PM/Stakeholder ที่ต้องร่วมประชุม วางแผน คอมเมนต์ ดู flow มักพอที่ Collab seat หรือ View (ถ้าดู/คอมเมนต์อย่างเดียว) อีกจุดที่คนพลาดบ่อยคือ “คิดว่าเพิ่มคน = ต้องเพิ่ม Full seat” ทั้งที่จริง ๆ การเพิ่มทีมมักเพิ่มคนที่รีวิว/คอมเมนต์/วางแผนเยอะกว่าคนออกแบบ ทำให้การผสม Dev seat + Collab seat ช่วยลดงบรวมได้มาก โดยเฉพาะทีมที่มี dev/pm เยอะกว่า designer เรื่อง AI credits ผมแนะนำให้เช็กนโยบายของทีมก่อนเลยว่า: 1) จะให้แต่ละคนใช้เครดิตของตัวเองตาม seat หรือ 2) จะซื้อ additional credit เป็นกองกลาง (pool) แล้วกำหนดเพดานการใช้ต่อเดือน เพราะถ้าเปิดแบบ pay-as-you-go แล้วไม่มีเพดาน วงบอาจบานโดยไม่รู้ตัว (ยิ่งช่วงเร่งงาน) สุดท้าย ถ้าอ่าน/ฟังชื่อ Tanon Techanithijinda แล้วสิ่งที่อยากได้คือ “แนวทางเลือกแพ็กให้เหมาะ” ผมว่าคำตอบคือกลับไปดู workflow ของทีม: ต้องการแค่ส่งมอบงาน (hand-off) หรือเริ่มมีหลายทีม หลายโปรดักต์ ต้องแยกสิทธิ์/จัดการ library/branch/permission จริงจัง ถึงค่อยขยับจาก Professional ไป Organization/Enterprise จะคุ้มกว่า และไม่ต้องจ่ายเต็มทุกคนตั้งแต่วันแรก