Built on StreamTask
Five things businesses asked us to build.
Visit planning, CV handling, requirement profiles, comments with likes and time stamping by QR code. Each began as a conversation about how a business actually works, and ended as a part of their own StreamTask system. Companies and people below are fictional; the configurations are real.
For a sales team
Visit planning across the year.
A distributor’s sales team plans how many visits each customer office should get over the fiscal year, month by month and by type of visit. Completed visits fill in from the visit log, overdue ones turn red, and a salesperson’s change to the plan waits for the manager’s approval. The visits themselves are logged from the phone, often by voice.
One matrix per fiscal year: customer offices down the side, months across, product and project visits apart.
Drag a planned visit to another month; approve a colleague’s changes in one click.
Dashboards show planned this year, fulfilled so far and the customers that are lagging.
This fiscal year
Visit planning
- All types
- Product
- Project
- Lagging only
- Changes to approve (2)
- Product visit
- Project visit
- Other
- Planned
- Overdue
Example data. Every company, person and figure shown is fictional.
For a consultancy
CV handling without the licence per user.
Every consultant keeps one master CV and updates it themselves, with a live preview and a list of what is still missing. The bid team sees at a glance whose CV is fresh and whose certificates are about to expire, and exports a tailored Word or PDF copy per tender without ever touching the master.
One master CV per consultant; tailored copies per tender, so the original is never edited by mistake.
Freshness and expiring certificates visible in the list, not buried in each profile.
Word and PDF in two languages, two templates, and a sharper profile text on request.
Consultants
- Emma HollisSenior energy engineer · Leeds · 14 assignmentsFresh
- Daniel MercerSenior corrosion engineer · Manchester · 22 assignmentsAgeing
- Priya NairEnergy systems consultant · Leeds · 9 assignmentsFresh
- Tom AskewDistrict heating engineer · Sheffield · 17 assignmentsOver a year
Master CV · Emma Hollis
- Person and photo
- Profile texts3 roles
- Skills28 rated
- Assignments2 without description
- Education and courses
- Certificates1 expiring
- Languages and tools
Certificates expiring
- AMPP corrosion assessorDaniel MercerExpiring
- Pressure equipment, cat. IIEmma HollisExpiring
- Site safety cardTom AskewExpired
Export
- Word
- English
- Standard template
- Compact template
- Black and white
Example data. Every company, person and figure shown is fictional.
For the same consultancy
Requirement profiles, read from the client’s documents.
Upload the tender documents and the system reads out a requirement profile: what is a must, what is a should, what counts as added value and what will be evaluated. It then ranks the consultants who fit, shows which requirements each one covers, and lets the team build the tailored CVs and the offer from the same page.
Every requirement keeps its source reference, so the team can check it against the document.
Candidates ranked 0 to 100 with the requirements they cover and a one-line reason.
A thumbs up or down on a suggestion teaches the matching what this team values.
Tender
Requirement profile
- R1MustAt least ten years of experience in district heating distribution. [Tender 3.2]
- R2MustCertified corrosion assessor (AMPP or equivalent). [Tender 3.4]
- R3ShouldExperience of condition surveys in networks older than 30 years. [Annex A]
- R4Added valueFamiliarity with the client’s GIS environment. [Annex B]
- R5EvaluationQuality of the proposed method and reporting. [Tender 5.1]
Suggested candidates
- Daniel MercerIn selection88Led two network condition surveys since 2019; AMPP certified until 2026.R1R2R3
- Priya Nair74Method lead on three reporting-heavy studies; no corrosion certificate.R1R3R5
- Tom Askew61Long network experience, GIS work for the same client in 2023.R1R4
Example data. Every company, person and figure shown is fictional.
For the same workshop
Time stamping by QR code, payroll ready.
A printed code at the door is all a worker needs: scan it, and the day starts. The app shows stamped in since when, hours so far against the schedule and breaks taken, and stops the running job timer on the way out. The office sees attendance per person against the schedule, checks the stamps made without a code, and exports a reviewed month to payroll.
One code per door and purpose: in, out, break. Codes can be replaced at any time.
A stamp without a code is flagged for the office, never blocked: the worker is never stopped.
Each month goes draft, reviewed, exported to payroll. Re-exports send only the new days.
Stamp
Door code
Your stamps
- Wed 28 Oct07:02 in · 11:45 break 15 min · 16:10 out
- Tue 27 Oct07:10 in · 16:02 out
- Mon 26 Oct06:58 in · 15:40 out · no code, notedTo check
Time and attendance
| Person | Mon | Tue | Wed | Thu | Fri | Week | vs plan |
|---|---|---|---|---|---|---|---|
| Jonas Reid | 8:05 | 7:55 | 8:10 | 7:50 | 6:30 | 38:30 | +0:30 |
| Anna Price | 7:50 | 8:00 | 8:20 | 8:05 | 5:45 | 38:00 | 0:00 |
| Marcus Hale | 8:00 | 7:57* | 8:00 | 8:10 | 6:05 | 38:12 | +0:12 |
| Lena Moss | 7:40 | 8:00 | 7:45 | 8:00 | 6:00 | 37:25 | −0:35 |
Payroll report
- Jonas ReidOctober · 164 hReviewed
- Anna PriceOctober · 158 hDraft
- Marcus HaleOctober · 160 hExported
Example data. Every company, person and figure shown is fictional.
What it costs
Your own system, for €120 to €450 a month.
Businesses get their own StreamTask system, configured around them, for between €120 and €450 per month. Where you land in that range depends on which parts the system holds and how much data you need to store. The systems on this page all live inside it.
No per-user licences to count. One system, one monthly fee, introduced through a guided implementation.
Currently onboarding selected businesses.
StreamTask is currently introduced through a guided implementation. We work closely with each business to configure the right structure, migrate existing information and prepare the system for launch.
Tell us a little about your business and we will get back to you personally.
For a workshop
Comments with likes, where the work is.
Workshop and office talk in one feed, attached to the order or the job it is about. A heart says “seen and agreed” without another message, replies stay under the comment, and a mention reaches the right person. Filters show what is yours, what mentions you and which jobs are waiting for parts.
Comments live on the order and the job, and in one shared feed for the whole team.
Likes, replies and mentions, built for phones in a workshop: no hover, big targets.
Filters for mine, mentioned, waiting for parts and stopped jobs.
Talkworkshop and office
Impeller is cracked, new one ordered. @Erik can you tell the customer the launch moves to Friday?
Done. Customer is fine with Friday.
Antifouling finished, photos are on the job. Ready for the water test.
Down to the last two oil filters, added them to purchasing.
Waiting for parts
Example data. Every company, person and figure shown is fictional.