Project access
Choose which projects each group can open. A coordinator on one bid does not need to see the rest of your pipeline.
Company licensing
One license for the company. Not a seat counter.
Your organization pays once, or monthly. Employee accounts, groups and permissions are planned so you can decide who opens which projects, menus and panels, with no per-seat fees and no licenses to reassign when staff change.
Planned: employee accounts and roles
Available: local-first desktop app
Status: the company license model and prices are proposed. Employee invitations, groups, roles and permissions are on the roadmap and are not built yet. Everything on this page about them describes the plan.
The model
One organization. Many employees. You set the boundaries.
The company holds the license. Employees belong to groups, and each group carries permissions over projects, menus and panels.
Your company
One license. One legal organization. Unlimited named employee accounts.
Group
Estimating
Senior Estimator
Estimator
Estimator
Projects
Project AProject BProject C
Menus
TakeoffMarkupExport
Panels
Takeoff tableTool palette
Group
Project management
Project Manager
Project Manager
Projects
Project AProject B
Menus
MarkupExportTemplates
Panels
Takeoff tableTool palette
Group
Review and field
Viewer
Viewer
Viewer
Projects
Project AProject BProject C
Menus
ViewTakeoffExport
Panels
ThumbnailsBookmarksTakeoff table
Permissions Planned
Three things an administrator will control.
Permissions attach to groups and roles, not to individual seats you have to count and move around.
Menu access
Show or hide menus and commands. For example, keep Export and shared-template editing out of reach for view-only accounts.
Panel access
Decide which docking panels appear, such as the Takeoff table or Tool palette, so each role sees a workspace that fits its job.
Role templates Planned
Suggested starting points. Fully customizable.
Six templates to start from. Edit them, duplicate them, or build your own. They are suggestions for how companies commonly split work, not fixed tiers.
Owner
Holds the company license and billing. Can do everything an Admin can, and can hand ownership to someone else.
License and billingAll projects
Admin
Invites and removes employees, builds groups and roles, and sets project, menu and panel permissions.
EmployeesGroups and roles
Estimator
Creates takeoffs, markups and estimates on assigned projects, and exports the results.
Assigned projectsTakeoffExport
Senior Estimator / Reviewer
Everything an Estimator does, plus reviewing and approving estimates and editing shared company templates.
ReviewShared templates
Project Manager
Reads estimates and quantities for assigned projects and adds markup, without access to company settings.
Assigned projectsMarkup
Viewer
Opens assigned drawings and reads existing takeoffs and markups. Cannot create or export.
View only
Suggested defaults at a glance
| Permission | Owner | Admin | Estimator | Senior / Reviewer | Project Manager | Viewer |
|---|---|---|---|---|---|---|
| Manage license and billing | Yes | No | No | No | No | No |
| Invite and remove employees | Yes | Yes | No | No | No | No |
| Create groups and roles | Yes | Yes | No | No | No | No |
| Open projects | All | All | Assigned | Assigned | Assigned | Assigned |
| Create takeoffs and markups | Yes | Yes | Yes | Yes | Markup only | No |
| Review and approve estimates | Yes | Yes | No | Yes | Read | No |
| Edit shared templates | Yes | Yes | No | Yes | No | No |
| Export and print | Yes | Yes | Yes | Yes | Yes | No |
Suggested starting defaults. Every one will be editable.
Status
What exists today and what is still planned.
Company licensing is a commercial model first and a product feature second. Here is the honest split.
Local-first desktop foundation
Today's pre-release build already has the toolset your company would license.
- Windows desktop app that works with local files
- Takeoff, measurement, PDF markup and formula-based pricing columns
- Tool sets and Workspaces that can be exported, imported, shared and locked
- Shared stamp folders, and Workspaces you can lock and share
- Share a plan set in a network folder, with sheet check-out so two people never save over each other. No server.
- Signed license files that work offline, with a request file for computers that never go online
Organization layer
The accounts and controls that make one license work for a whole team.
- Company license purchase, billing and an owner account
- Inviting named employee accounts, with no per-seat fees
- Groups and role templates, fully customizable
- Project, menu and panel permissions per group
- Centrally managed company templates and assemblies
- Removing an account when someone leaves, with no seat to reassign
Offline and security
Local-first. No forced cloud.
Company licensing should not mean your drawings leave your network. Your drawings and takeoffs stay on your computers.
Works without a connection
Measurement, markup and estimating run on your PC against files you keep, so a job site with no signal is fine. A computer that never goes online is activated from a request file.
Your files stay your files
Takeoff data is saved inside the PDF as standard annotations, so other viewers can show it. There is no required server or cloud account to open your own projects.
Hosted services are optional
The only hosted pieces on the roadmap are optional add-ons, such as Secure Document Exchange and archive storage. You can run the company license without either. Concept
How the license works
A one-time license is a signed file checked on your own computer: it never needs the internet and never checks in, and it is never switched off. A subscription will check in online from time to time; if it lapses, Kisheet falls back to Kisheet Free (planned), so you can still open, read, mark up and sign your PDFs. Not decided yet: how planned permissions will be enforced on computers that stay offline, and what audit trail admins will get. We are not making security certification claims.
Company licensing FAQ
Questions we expect from owners and IT.
What counts as a "company"?
One legal organization, the entity that holds the license. Unlimited named employee accounts belong to it. How affiliates, subsidiaries and joint ventures are treated is not decided. If your structure is unusual, tell us so the terms can cover it.
Is there a per-seat fee for employees?
No. The proposed Company price is a monthly price a month or a one-time price once, for the whole organization, and does not change with headcount. These are proposals, not final prices.
Can I buy the Company license once instead of subscribing?
Yes, that is the proposal: a one-time license with 12 months of updates, never disabled when the update period ends. Renewal pricing isn't set yet. A subscription is the alternative. See pricing.
Can my company use this today?
Not yet: Kisheet is not released. The core desktop toolset exists, but there is no download or checkout yet, and employee accounts, groups and permissions are not built. Until they are, a company-level license is a commercial arrangement rather than an in-app account system.
What happens when an employee leaves?
The plan is that an admin removes the account. Because there is no per-seat count, there is no seat to reassign or pay for. Your project files are local files your company keeps.
Do contractors and 1099 workers fit under a Company license?
Not decided. The license is built around employees of the licensed organization, and outside contractors will be addressed in the final terms. An independent contractor can ask us about independent pricing.
Does my IT team need to run a server?
No server is planned for the base product. The app is local-first. Any hosted component would be an optional add-on, and the company license does not depend on one.
Can I use my existing CRM or workflow tool?
Yes. Nothing about the company license replaces your existing tools. Workflow add-ons are optional, and you never have to buy features that duplicate what you already run. See add-ons.
Get Kisheet
Tell us how your company is organized.
Team size, trades and the tools you use today help us shape roles and permissions around real firms.