Blog
Work that does not scatter
Tasks, access, the demo, and sprints. Applied notes with screenshots, not a brochure.
Software teams should not carry the roadmap on slides
When issue tracker, wiki, and slides are three sources, the sprint lies. In Ontra, feature, task, and doc are one tree. The backlog is not a graveyard; it is the line in front of a locked sprint. The decision does not stay in a GitHub comment; the acceptance sentence lands on the card. Tech debt is tagged, not a secret list.
Read post
Field teams on the map, office on the list, same work
Construction and service work need a location. Ontra’s map view shows where the task sits; status does not contradict the office board. The pin sits on the task card, not in a separate GIS. Photos land on the card. A technician does not see every project — only assigned work. In the offline reality a second “field Excel” is not born.
Read post
7 days, no credit card: do not tour the showroom, move work
The Ontra trial does not ask for a card. When time ends the app locks; data is not deleted. Fill the demo week with a real project: roles, the live sprint, the docs tree, the first report. Taking a card is a “maybe we’ll use it” hold. Ontra wants the work to sit first. Subscribe and return to the same records; there is no second setup.
Read post
Per-seat price: grow by adding a person, not switching a package
Features sit on one plan. Growth is a new seat, not a new package. Ontra keeps the price explicit; there is no hidden add-on. Board, docs, sprints, reports, and fine-grained access sit on one plan. A viewer is still a seat. The seat starts when the invite is accepted. Close it when the internship ends; the price drops that month.
Read post