01
Ready for pilotPhoto documentation
Sort site photos against the operator’s guide, review the matches and export the named set.
Explore the application
Custom software for telecom teams
Less manual work between
the site and the office.
01 / Solutions
Software around your workflow.
Four examples of what I can build for your team. Each starts with a specific task and fits the way you work.
02
Custom developmentDocument answers
Help field teams find answers in technical guides, in their own language, with the source attached.
Explore the approach03
Custom developmentRequirement checks
Compare survey reports, designs and material lists. Give engineers a clear list of discrepancies to review.
Explore the approach04
Custom integrationSystem integrations
Move reviewed results into Microsoft 365, your ERP and operator systems without re-entering the same information.
Explore the approach02 / Built at Pylaros
Photo documentation, built for review.
Site photos become an organised set for office review. The application matches them to the operator’s guide and applies its naming rules.
Try it yourself
Take a batch from field to handover.
Five sample photos. Your decisions.
No account needed.
Try the interactive demo - 01 Add the sample batch
- 02 Correct and confirm matches
- 03 Download your reviewed set
Does the team need to install an app?
No. The office sends a link for the site. It opens that one site only, expires, and can be withdrawn at any time.
How are mistakes corrected?
The reviewer can change any match. That decision holds on later runs. Photos the model cannot place go to Unfiled with a reason.
Which operator guides does it support?
I configure it for your operator’s guide. The first requirement pack uses Telenor’s as-built guide for mobile sites.
What can we export?
A zip of named photos, including an Unfiled folder. You can limit the export to photos a reviewer has confirmed.
The person behind PylarosBuilt from
Built from
telecom experience.
I’m Lukas, the founder and developer behind Pylaros. I know the work on the tower and the paperwork that follows. That experience shapes the software I build.
You work directly with me, from the first conversation through development and testing.
Meet the founder03 / Working together
From the first conversation to working software.
Start with one task worth improving. We agree the scope and test the result with the people who will use it.
Understand the task
Show me the process, the people involved and a few real examples. We identify the work to improve and what a useful result looks like.
Agree the scope
Before development starts, we agree what I’ll build, how we’ll test it, the price and the delivery plan.
Build and review
I build the software and review progress directly with you. Your team tests it on representative work, and we resolve the findings before handover.
Put it to work
I prepare the software for use and hand over the agreed documentation. We define hosting, ownership and ongoing support in the project scope.
04 / Get in touch
What needs to
work better?
Tell me which task slows your team down and what you’d like to improve. A few sentences are enough; you don’t need a finished specification.
I’ll reply personally with any questions and a practical next step. If a call would help, we’ll arrange one by email.
Or email me directly:
hello@lukasja.dev