Name: Never miss a billable hour with 7pace
Uploaded: 2025-12-04T15:16:11.156Z
Duration: 55 min 36 s
Description: Never miss a billable hour with 7pace

Transcript for "Never miss a billable hour with 7pace": Okay, everyone. I think that we're right here at 09:00. We'll give a couple more minutes just for people to join, and then we will go ahead and get started. Alright. So we'll go ahead and get started today. Thank you everyone for joining the webinar with Appfire and SII. Today, we'll be talking about how to never miss another billable hour with seven PACE. And we've got Roman and Jimmy here with us, and I will let you guys kick us off. Roman, why don't we start you very much. Thank you very much. So if I can have. my. first slide. And I would like I would like Jimmy to start maybe introducing himself, with you? then then I will, go next. Okay. Can you all hear me well? I can. think so. Can you give me the next slide, please, Roman? So my name is Yimi Wiekmann, and I come from SAI. And SAI is I'm more specifically, I'm actually from SAI Sweden, which is part of SAI Poland, which is a part of the larger group from France. So SAA Poland is a company that started in 2006, and we have 7,300 employees at the moment. And we are one of the leading technology consulting firms in Poland. So if I can have the next one, Roman. Yep. And when we say that we are the leading consultant, we have, a large offer. We usually, brand ourselves as a one stop shop. So we have basically everything you need, for everything that you have within your company. So if you need anything from development to ecommerce and to embedded systems to to, support or if you have artificial intelligence or cybersecurity, then we have it. And my part then belongs to the enterprise software branch where we have the Atlassian part. So we take next slide. And for my computer center then, where I belong to, we are around 50. We are more than 50 certified specialists at the moment. We are hiring quite actively at the moment. And we are also one stop shop. So basically everything that you could possibly need when it comes to Atlassian, consulting, implementation, migration, maintenance, and so on. We are capable of handling that. NS AI is a platinum partner, and so we are the highest tier that you can be as a partner with Atlassian. And we are specializing in cloud migration and software, development. So if we take next one. So who am I then? Who comes from this, company? Well, I'm within the SAI architecture, or their structure. I'm an architect. So I call myself normally an expert because I worked with Atlassian platform for more than thirteen year, and I put in a lot of hours in that, time span. And I'm you might see that I have a little bit of gray in my beard as as well. So it means I've been around for a while, and one of my bigger strength, is that I have worked professionally not just within Atlassian, but I've also worked in pretty much every position you can have within the, delivery process within a company. So product management, program management, roll up management. I'm a certified requirement analyst. I'm a school UX, UI, and CRO designer. I worked several years as a tester. I've spent more than twenty years hosting my own web hosting business. So I have a few network certifications, and I've played around a lot with the networks and, server roles. I've spent a lot of years since 1996, I think. I started as a front end developer. I still write code every week on my own website. And I also work quite a lot with work processes, and I usually are at the higher level when it comes to work processes. So, the l one, l two levels, and not just down on the l three and l fours in Atlassian. And I'm also an Atlassian content creator, so I do a lot of YouTube videos and write articles. And sometimes I get the privilege of getting called in to to help, marketplace partners or even Atlassian as, an expert, to help further their products. So that was all about me and my company. So let's hand over to you, Roman, and let's see here who you are. Yeah. Thank you, Jimmy, or Yimi. What do you prefer, actually? I haven't asked, and we've met mean, we'll a few. Yimi. Yep. Alright. Good. So, sorry for that. So my name is Roman Fianta. I joined Appfire more than three years ago. I'm leading product management in the time tracking category there. Although, like, altogether, I have more than five years, many more than five years, I'm also graying, years experience leading products. Before Appfire, I was working for a company that used Jira as their work management tool, and I did Jira administration work as a side job. And it's actually a kind of a hobby, so that also made me pretty fluent with, both Jira and Confluence. In case in case you don't know, Appfire, it's a company with the biggest footprint in the Atlassian app marketplace. So maybe even if the name does not ring a bell, I think the names of some of the apps will, like GMWE or former Bob Swift apps or Big Picture. And I think that's, that's enough about me. Well, it's good to have you as my my partner in this webinar, Roman. And so we're here to talk a little bit about one of one of your many apps that you have because you have quite a few. And the app we wanna talk about today is the seven PACE. So can you tell me a little bit what that app is? Of course, Sevenpase is a time tracking app. So what it does is that it lets people track time within Jira, and their managers can then see this time and use it for reporting. We know that people who actually want to track time are a really rare breed, so our focus is to make this experience as frictionless as possible. And we have been on this mission for many years now. We started in Azure DevOps. We are numb the clear number one there. We replicated the success, like, two years ago in monday.com marketplace, where we are the fastest growing time tracker. And just recently, we have decided to make the move to Jira as well and disrupt the stagnant time tracking market there. So I'm a little bit curious now. You have already been you're already on on other markets. So what is the, decision or your thought process here? What what made you consider to also invest time and and money now to to bring this to Atlassian? That's a good question, and it's also it also brings me to the topic of this webinar about never missing another billable hour, which is kind of our mission. Because, believe it or not, you mean there are still companies, including the large ones, sometimes especially the large ones, who track time in spreadsheets. You may know this feeling, it's the end of the week and managers are chasing their people to fill in their timesheets because they need this time to send invoices or billable hours to customers or calculate project budgets, or calculate payroll. The work in these spreadsheets is by default disconnected from the actual items in the work management tool like Jira, so from items from projects and clients. And people have to rely also on their memory to report their work hours accurately. As a result, it's estimated that 20% of billable hours get lost in this cumbersome process, and that's that's a lot. If you think about that on a scale of $10,000,000 project, that's 2,000,000 of loss. And that's actually the reason of existence of time tracking apps, that they are that's why there are so many, because when your work is connected, or sorry, where your time is connected, to your work items, it brings also lower friction, better attributions to projects and clients. When it's, you know, a part of your workflow, you just you just achieve a better accuracy, which effectively cuts the lost hours to a half, if not even more. So here comes my first recommendation actually of this webinar: if by any chance you are still using spreadsheets, don't. Like check check the marketplace apps and try using some integrated app. Start with one team only, see if you get more accurate data with less work, and my guess is that the answer will be yes. And, I'm from Appfire, so you probably expect me here to promote our App7 pace here, and you're not wrong. We believe that this five to 10% of billable hours lost is still too much. Ideally, we want to see zero here. How do we want to do that? By removing guesswork and friction as much as possible, for example by integrating users calendars, by providing some smart suggestions, we really strive to remove this remaining friction there is and eventually eradicate the need for time tracking completely. That's what we believe is the right answer. We are not there yet, but we're making good steps in this direction already, as I will show you later in this webinar. And this is probably the second takeaway. When using an integrated app, it needs to feel like a part of the workflow with as little friction as possible. It needs to encourage users to record time while they are doing their work in this work management tool. So if you try to remember what you did last Monday, it's it's really hard, I guess. I don't really remember what I worked on last Monday. But when I record these hours, when I'm working on this task, it's just, so much easier and more accurate in the end. Sounds like a dream, for a lot of people to have a tool that can can do this, pretty much, on the fly there. So does this mean that, I don't have to track them manually? So how does that work? Well, full disclosure, this still needs, some manual effort. It would be great to have zero work, but right now the manual effort is still there. Let me let me show you in the app instead of just know, talking high level. So I'll move to the right screen here. I just need to, yeah, switch the screens. So, this is this is seven pace, a time tracking app, and I'll show you what we what we offer to people. So let's start with a project. I'm working on Jira, I'm working on this project to conquer the world. And today, let me open a Kanban board, I was working on hacking another TV station, right, so hacked maybe, I don't know, ABC, whatever. Right? A TV station. When I worked on this, I can also track my time directly here. How do I do that? I just click, yeah, add time, so two hours, and it's there. If you if this was too fast, that was intentional because I wanted to show how easy it can be to track time. I just tracked two hours. So let me maybe do it again, but slower. So I clicked on add time in this side panel. I selected two hours. Maybe it was three, actually, so I can just click here. Maybe one and a half, right? It's still super easy. And I click save, and the time is recorded and attributed to the right item. I just duplicated by accident or by wanting to show you how easy this was. Let me remove one of these, and it's really still as easy as that. So that's one way, like doing it directly where you work with as little friction as possible. You may have noticed, this, no, Billable time picker is not here. I will show it later. So we will get to how to track billable time and not billable time later in the webinar. But, first, let me, show you how to see all your work. Because this was work on on one item. It doesn't show you how you actually spent your week. So what if I need to have this overview? I go to the seven PACE app, and here I can see three levels of overview that I can use, like a monthly view, very high high level, weekly view, or timesheet view. Now my favorite is is the weekly one, and I will show you why. Maybe I will also make this a bit larger so that it's easier to read. So, yeah, my favorite parts here. First of all, you may have noticed that I connected my calendar. I have my calendar here, like my fake calendar. My usual one is much more populated, but, yeah, this is my calendar, and I can see the items here. What I can do is that I, I just select this calendar event, click add time, click save, and that's it. You know, very, very easy. You could have noticed that the item was selected automatically. That was because this is a recurring event, and for this recurring event, the system remembers how I did track time in the past, and, just reuses it for future records. That's not all the magic that's available here, though. What if I need to track time on on all of these? Well, I can I can do this one by one, and it's still really quick, or I can do this and in in an even faster fashion? I can just duplicate to other days, and maybe this meeting was actually longer. And maybe here it actually didn't take place. Right? And I click save, and I already, created a lot of, like, time entries in a few clicks. And, you know, there's more coming, but I think, I'll pause here and wait for your other questions. Yeah. That sounds like a real thing time saver if you excuse the pun here. But, I especially like this calendar view because like you, my calendar is a mess. So does this mean I can actually use the calendar here now to plan my work? Not exactly. Like, the main idea of this calendar integration and the main benefit is that it helps you remember what you worked on so that you can more accurately track time. Our goal is accuracy, not really predicting and and the future. The calendar integration is therefore one way, so Sevenpase consumes the data only. But actually, like, feel free to plan your week in your calendar. You will then see the events in Sevenpase even if it's in the future. You know, if I switch to the next week, you you will still see the events. You don't have to track time on them until this day comes, but, the events will be there. And, by the way, the calendars, of course, remain personal. Just a side note here. It's not that your manager can suddenly see all the details about your calendars. We don't want people to feel surveilled or anything. Time tracking should be about getting insights, not introducing this big brother thingy. So if employees then understand the benefit and managers do not misuse and cannot actually see our calendars, the adoption gets better, which again further improves accuracy, we believe. But going back to the calendars, speaking about accuracy and adoption, it even suggests the right items. This is something I wanted to show you. So you can here see this meeting one to one with Konya, and inside of the description you can see discuss this, you know, Jira item. So if I click to add time on this one, the system will automatically find out that the item key was used in the description and pull the right item accordingly, and it can just save time on that. This is something I didn't show in the previous part, I believe. Yep. That makes perfect sense. And for me, having, the ability to plan a little bit in the calendar here is great because my memory is not what it used to be. I also think that what you've shown so far is how easy it is to use this tool, which is great for the developers, but, it is also, one of the main purposes for this is to make it easier also for the managers. Right? So we are showing now the calendar, but what does it look like for the managers? What kind of use do they have, and, what can we expect from from the views where everything comes in from all the users? Now, for managers, we have a view called times explorer, which shows all time entries across all projects from this Jira site in one view. So let me select a wider time range because this is still a testing instance only, so there are not so many records if I select just the last month. So this shows the records from the whole year, right? So from all projects as you can see the here from all, all people including Lisa who's on a call with us today, including, you know, all all the other information all in one place. So this is what managers use to get a sense how time was spent. That looks great. Can I customize this view? So let's say I want to see only the information from one project, for example. Is that possible? Yeah. Yeah. Of course, it is. No nobody would probably want to just sift through this, you know, thousands or tens of thousands, of records. So, of course, you can filter. You can do it by clicking on this button. And let's say I want to filter only time tracked on project, called conquer the world. So like that, I could I could filter the items, and you can see that only items or, like, work logs from this project are now visible here, and it cost me a few clicks only. If one project is not enough because I'm managing more projects and I need to, I don't know, create invoices, for example, for this project, I can just select, other ones as well. So I just add it to other projects, and I can see them here. That could get messy. Right? So this is still a long list. So, what if I want to see how much time time was spent on this project? I can group either by typing a name here or just by clicking on this button. It will group time by projects in, yeah, in one click in this case. If you're like, more like a people manager, not a or sorry. First of all, what if you want to see breakdown by people, how they spend time on these projects? So you can do that as well. You just add a new group. You can select or just type, I prefer typing it's much faster, and you can see like how much time particular people spend on this project, or you can filter down people as well if you wish. And if you are more a people manager, not a project manager, so your main focus is how much time people spend and only then you want to see on what projects, you can do that as well. So you just move person up and the order will switch. So you will see first people and then projects, easy as that. That's amazing. But do I have to do this every time, or can I save this view somehow? You can save these views by clicking here. I already have quite a lot of them. So you can either like save changes to an existing view, or you just save a new one. So like, I will just create a new one here. I will save the layout, and you know if I go somewhere else, I go back here, the last view is remembered. If I go back to default view and then I decide I need to jump back to this, to this one, I can do that and the system remembers it, including the time range. That's super slick. Can I ask something? I think I spotted that you had data from Jira in here, not just from from server base. Can you actually use, Jira items or your custom fields here? And if so, which fields can we actually use? You can use any Jira or almost any, Jira custom field. Like, so all the native fields and the custom fields from Jira, you can see them here. So, let me show first this one, this cogwheel. You can select what seven page columns you want to show, and you can select what Jira columns you want to show. And you can see, like, there's a lot of them. And by the way, big picture columns, like, one one column, big picture teams as well here. So let's say you have a customer field that's set up on epic level and propagate it to all children items, like on this item, conquer the world. Right? So maybe I show on one item for context. So I have the customer field here. And so if I want to let's say I want to group by it. Right? So I just find again, I prefer typing, so I add customer here and group by it as well. Maybe I'll want to remove the person. Oh, I removed project, didn't I? So let me add project back. And, so for this project conquer the world, I can see how much time was spent on this customer and this customer. So that's that's one example. And, once I have this, now I can just select this and, send a list of billable hours for this period to these customers easily. But let's take this one step further. What if I want to distinguish between, for example, operational and r and d expenditures, typically referred to as as CapEx, OPEX per customer? I can still do that, because I have and again, I have this field like CapExopex on, on an epic and and story level. So what I can do is pull in yet another Jira field and group by it as well, you will be able to get a breakdown of CapEx, OPEX per customer, again, with a few clicks. I I know I'm repeating myself, but we really strive to make everything as easy as possible. And, the last thing I wanted to show, like, this was the more complicated setup, you can also have like an, let's say, a more straightforward setup where you just track, like, billable flag on items, and then when you track time on these items, you can again group in Times Explorer, according to this billable flag. Great. I since you mentioned billable here now, let's say I work for a smaller organization. I don't want to have a lot of, red tape going on. I want the users that work in the product to determine for themselves, is this billable or not? Is this supported directly out of the box or something I need to configure? Or how does it work with with the permissions to actually set what is available or not? Yeah. Good question. And we hear this quite a lot. So typically for these smaller teams with high agency, this is this is a favorite option. If you install seven Pays, you will by default have this billable hours field. I have it disabled right now, but let me enable it back. Right? So if you install some and paste, this will be there by default. In this custom field section that admins can can enter, you can create up to 10 custom fields, like toggles or drop downs, and decide which ones of them are required and which ones are not. The limit of 10 is like that's that's a lot. Right? I I really don't recommend you asking people fill in ten ten fields when entering time that would defeat the purpose, but, yes, like, for these smaller teams with high agency having this billable hours may be may be a good option that we see. And of course then in Times Explorer, if you have this billable field, filled in, you can oh, let me stay in the default view. You can group by it here. Right? So, you see these custom fields here. You can group by them. So build our CS are not set, for some older records or no, of course. So just maybe to give you a wrap up, depending on the size of your company and the way how you work, there are, like, three levels how you can distinguish billable time, I think. Right? So let me take the a broader answer to that. So first of all, either you just know that's the first the first option is. You just know that certain projects are billable, like the client projects, and certain projects are not. Right? So let's say this conquer the world, this is something I can build, but then I can have, like, internal project here, maybe vacations, etcetera, or, like, internal meetings or building an internal tool that I cannot really build to customers. So this is the the easiest way, probably. You just, you don't flag anything. You just know which projects are billable or not. And then in your reporting, you just, you just bill only for certain projects and the other internal ones, you don't send any invoices for. That's the easiest option. Then the second option is if you want to distinguish or when you want to distinguish billable hours more granularly, or you typically have, like, billable and not billable items within the same Jira project. So in this case that I demonstrated here, you can or sorry, here, let me open sheets. Do I have sheets here? Yeah. In this case, I would recommend using a custom Jira field on item level. Right? This way you still you don't ask people to think about billable time every time they track time because it's their own items. And using some Jira automations, you can just propagate that from the top level to the lowest level without any you know, hassle. So that's, that's the second option if you need to have billable and not billable hours within the same project. And then the third option was the one I showed a while ago, when you want to select billable or not billable hours, when you track time. So that's when, having these custom fields come in handy. Right? So users will just see this toggle and be able to set this on or off when tracking time. At this level, you can have billable and not billable items even on the same item. I would generally so these are these three options. Now my recommendation comes. I would generally encourage to move this build a decision to as high level as possible, because that means that people don't have to think about it, and it it just requires the least amount of maintenance and cognitive flow. Good. And since we are speaking now about billable hours, that's financial stuff we're talking about. And if you are sending a bill now with billable hours, no one can actually change it afterwards. So how do we prevent people from going in and changing things after you send something? Is there some kind of protection mechanism there? Yes. It is. Because it's a it's a frequent request, and, you know, if you mean it seriously with your financials, it's better to have some way of reviewing and approving and locking the time. We don't want to make this a tiresome process, but still some kind of process is is definitely, like, beneficial here. How we do that is, by having approval periods. So let me start with settings. Actually, as an admin, you can select whether you want to use approval periods or not. You can select cadence, weekly, biweekly, or monthly. You can even select like a split date, which comes in handy when you have a weekly cadence, but then on Wednesday there's end of month, you just need to close everything. So, we have you covered. You can just split the period that last day of the month. The periods, once you like, create them, are, automatically generated. You don't have to care, anymore about them. How does approval work? We have, like, two levels. First one is when let's start with the people manager level, actually. So you can see here that, I have, like, filtered people that I care about, including myself. I I care about myself, I'm I'm not, you know, hiding it. So what I, what I can see here is that for these periods, I can check how much time these people, edit. Right? And then I can either approve the time or or reject the time. If I approve it, it's locked for the person, and they cannot do any changes anymore afterwards. So that's the that's one level where managers just check what was done. Maybe they need to check the details because, you know, this number does doesn't tell a lot, of course. So they can check again in Times Explorer. They can even group if it's, like, better for them by days. Right? So they see day by day how much time was tracked. They can even see if it was, like, below the expected capacity or above that. And if they're happy, they can just they can just prove. Right? And then for the individual contributor, how it works is that they can see that the time entry here was approved, and that's it. I cannot do anything anymore here. When the next period comes, again, like, I as an individual contributor make sure that, you know, all the time here is tracked, you know, this would not be enough. I would typically, like, create, of course, like, or make it more carefully, and then I would just submit to manager, like this period. Or sorry, I can do it from here as well. Once I submit, I cannot, cannot do anything with it anymore. So this is how the process works: Contributors submit managers then check it in approval period. If they're happy, they just give, thumbs up here. Once all thumbs up are collected, what we then can typically see is that some kind of general manager or or, you know, finance manager goes here and locks the whole period, which means that even, like, nobody else can track time no matter if people, like, approved or, you know, submitted. It's just this period is locked. Invoices have been sent, so no more changes. This is how it's done. So let me ask the sneaky question then because we we have the ability to, to sort time, based on product. Can I also track how much budget I've spent, in a product using something in in seven days? You actually can by integrating with Big Picture, and by integrating also yep. Like, let let me demonstrate. That will be the best. Right? So in big picture enterprise, you have financial modules. So if you go to the financial module, you can see how much budget was allocated to a project, 50,000 in this case, and what was the actual cost. The cost is calculated based on tracked time. So let me just you you see 104 here. So if I open the project by hardware, which is one of the tasks in this project, and I track, I don't know, eight more hours, and I go back, then this total cost will be updated if all webhooks, etcetera, work as expected. It should. Right? So you can see the the, the budget increased. I'm way over budget, not because I'm a bad manager, it's because I really use it for demonstration a lot. So that's one point. The second point I wanted to tell is that, of course, you can use, you know, well, I I think we'll we'll get to that. Anyway, I said this requires big picture. Right? So in case you don't know big picture, I think we can we can have another webinar describing how big picture works because it it works pretty neatly together with SummitBase. Yeah. And I love big picture. Shameless plug here. I'm I've actually done an investigation in PPM tools in Atlassian ecosystem, and I'm planning a video for it. And I can happily tell you that Big Picture is the forerunner in that selection. So Big Picture is one of my favorite apps. But I want to touch a little bit on managers again here because you already mentioned that they love their Excel sheets. And no matter how much we try, they always pester us about how can I get my data into my Excel sheet, or they want to have some kind of integration to another system? What kind of support does Seven Pays have for exporting data or or connecting to another tool? Exporting to a spreadsheet was one of the first features we had back then many years ago when we started in Azure DevOps, so I I definitely understand. I use spreadsheets a lot as well. So we have this export, and it's like two level. So either you just want to export, you know, a subset of data. So let's say well, I need more data, so it's quite improbable that you would want to export the whole year, but let's say you wanted to export the last quarter for a specific customer or last month. Right? So what you can do is that you oh, again, filter. Oh, project is conquer the world. You filter, you can group by it. You don't actually have to, but you can. I just want to demonstrate that you can, and you can select all the items related to this project in this time period and just export it to a spreadsheet by clicking on this button. So that's how it is done when you want a subset of data, any subset of data. If you want to just export everything, you can do that as well by clicking here exporting all. So it's, it does something similar. You just export to a spreadsheet to an x l s x l x file. If you want to have, like, APIs and build your own integrations, yeah, you can as well. I actually encourage that. Spreadsheets are great for, you know, quick analysis of something, or creating some quick pivot tables, I totally get that. But if you really want to base your finance data and, like, use your finance data to payroll, for example, then the initial cost of building with APIs, will pay off really quickly multiple times, I think. So especially in today's world where I can write queries for you, it's not such a hassle anymore really to to create an API integration. So we have all the documentation and you can just pull all the work logs and custom fields from seven days and you can just then, you know, build your own integration. I like it. There are sometimes things that we do that we want to bill a customer for, but we might not have it. Well, we might not think of it as work. For example, when we have workshops or if we have events or something like that. What are your recommendation? How should we handle those? Should we create them as as items in Jira, or is there some other way to to do it? What what is your best practices for getting that data into seven days? As usual, there are multiple options. The one I would recommend and I'm usually recommending the most to customers is to create items in Jira against you against which you can track time. Yeah. I already, I think, show showed earlier this internal project where I have these PTO and company events and other tasks, and I track time on these. Why I believe this is the best option is that because if you track time with only a comment, like, you in theory can, like, you know, I can just oh, this is a closed period. This this one is not closed. So I can just track time with a comment. It works for smaller teams, like, that that's completely fine, but if you want to build some reporting on top of that, then relying on free text is just not good enough. The second best option is to use something called activity type. So still you don't have to have a Jira item, but you can set up an activity type in seven page. Let me just turn it on, I have it here prepared. And then when I go back to to weekly, for example, I can select this activity type like PTO or something else. That's the second option. But anyway, the best option I believe is to create these these Jira items like this an internal four here. It allows you to have more information about the item, like if it's CapEx, OPEX again, you can have it directly on the item, or maybe you need some other information. So I think it's, just the most reliable solution and one then where you can where you can report the best. And, actually, since you. asked about that, I think I I also wanted to show, like, or mention setup or other best practices, not only about related like, sorry, like internal items, but also some other best practices I would recommend. So I showed various ways how to use or how to set up tracking of billable time and CapEx of ex clients or customers. Also, like, flexibility is is great, but it it can also be a pain. So I would just recommend figuring out which case works best for you. Like, I had some examples here where I, where I wait. Let me just open this one. Where I track CapEx, OpEx on an item, and I have, maybe a customer field. So just I would recommend, like, figuring out which case and granularity works best for your company and then create a template project, and then reuse the same pattern across every project because, again, it will it will make reporting easier. So if you figure that billable flag on item serves you the best, use the same flag across all your projects. But like in the demo where I wanted to present multiple practices at once, and it was maybe, sometimes less. And the last recommendation, I should pause here, the last recommendation, I think I have is require as little as possible from the users. So the fewer fields, the better the adoption, the better the accuracy. So in case of these custom fields that I showed, I really recommend to to not have them unless you really need them. Right? So, of course, you can you can you can have them there. But if you don't, people just select an issue, add a comment, and they're done, and that's, like, priceless. Yep. The I fully agree with you. Simplicity is the best way, especially if we are forcing people to, to do more than they probably, are thinking that they they were supposed to do from the beginning. And time tracking is very difficult. So So I like the way you you have implemented this one. But let's talk a little bit about, more difficult items here now because one of the trickiest part when you want to add a new application is, of course, security. And I always have to convince cybersecurity then that whatever I want to add into my platform, it is not just a great product, but it's also safe and secure. So what kind of ammunition can I bring to my cybersecurity team to convince them that this is an awesome solution, with great security? That's a good question. I hope I have a good answer. Let's see. So if you type trust.appfire.com, you will find all the necessary information that that you that your Infosec probably needs. You can just send them this website. They may have to ask for like, they they will need to get access to get the real detailed documents because they need to, you know, do some signatures. But, yeah, just send them this page, and it shows you all the certificates that we have, all the, you know, third party, all the legal stuff, all under one roof. I like it. That will will probably please my my security team a lot. Well, nice setup also, nice overview of it. So let's talk a little bit also. We talked a little bit about how smaller companies can use the tool, and we talked a little bit about general. But what about the really, really big companies, like the multinational enterprise companies? Is there any size that you feel that, Seven PACE may not be yet the best solution for them, or will this be a perfect match for everyone? I think it's a perfect match for everyone. Like, it would be weird for me to say otherwise, but I really mean it. I mean, that's that's because, like, you can customize. Right? So you you can just install it, start using it, and never touch it, and it will work well. But in case you need more governance, like having these approval periods, if you need APIs, we have them. If you need, you know, to manage roles and permissions, which is also important, especially in the large companies, you can set this up as well. So I believe it really can work for any company, and it it can grow with you. I actually think so too after seeing, and also the performance that, even though you have not a ton of data, the performance is actually quite impressive. So you have showed a lot of amazing functionality here, and I'm I'm really impressed with with this app. But you're also hinting a little bit that this is quite a new app for the Atlassian ecosystem and that you have a lot of exciting things coming our way. Could you share a little bit about the future and what kind of road map you have? And perhaps also tell us a little bit about the level of commitment because this is one of many apps. So how do you how do you stop that one, and what is your vision for the future? Thank you for this question. I hope I'm prepared well. What we have, and this is public facing, we have a feature portal. So you can check what features we've delivered over the course of last well, since ever, basically, since we started with seven pays for Jira until this day. And you can also check what's in progress and what is planned and what is, like, not planned yet with some exact date, but, it's something that, is under consideration. What is good if if you're a customer and you find something that you need is that you can upload. Right? So you can just, click here, select that. Well, this is actually critical for me. I cannot use it without this. Give us a comment and submit, and we will know that, like, this is important for our customers. Or if you find out that something is missing here, you just can submit a brand new idea. And, again, our product team will will take care of that, probably get back to you and, ask for more details. So I would like to encourage everybody, to do this. This is, like, super important for us. We are kind of freaks, regarding user feedback. And then you asked about the level of commitment. I I think, like, this can already tell the level of commitment, like, a lot of major features delivered over the next, over over the past, twelve months, and we have we have also big features coming in 2026. This is not even a complete list, but at least it's a list where we are where we are, like, reasonably certain that we will deliver these. And the level of commitment is pretty high. It's one of the main focuses on that fire for next year. I mean, Seven Piece is one of the main focus apps. Very nice. And, working with, with you and the rest of the Appfire team for for preparing for this webinar, I can tell that you're really committed and and really, engaged in this product. So I actually don't have any more questions. So should we check to see if anyone who's watching have any questions? Yumi, sorry, but I actually have a kind of a small wrap, up with. You have one more. Yeah. Yeah. So, let's do a small wrap up and then then, let's continue with questions because I love to hear some. So some kind of takeaways that you can take from this webinar. So first of all, I would recommend use an app. That's my number one takeaway. Use an app, not a spreadsheet. If you're not using an app yet, then this should be your important the most important takeaway. Of course, that is if you need to track time. It's perfect perfectly fine not to track time in case you don't have use for it, but in case you bill customers, or do payroll, or track project budgets, you will need your track time, and in that case don't use spreadsheets but an app. The second one: find an app with the lowest possible friction because it maximizes accuracy and adoption sorry, adoption and therefore accuracy. The next one, people don't like to be controlled and surveilled, so use a time tracking use time tracking for insights and for credible reports of billable hours, for example, not to reprimand people about the length of their lunch breaks or something. The next one, decide whether you want to distinguish billable attributes on a work log item or project level, or if you want to distinguish it at all and choose your solution accordingly. Use Jira automations. In case it's on item level, I really recommend using some kind of automation, so either Jira automations or some of the marketplace apps if you need more control and flexibility. Then always connect your track time to something, ideally Jira items. It may be also activity type, but don't let just if you need robust reporting, tracking on comments will not really do the trick in most of the cases. The next takeaway is lab managers review time per video per video per video per video I cannot say this word. So regularly, let's say yeah, yeah, yeah, another word. So periodically yeah. Not good, but anyway. So frequent, in some setup frequencies, regularly, because if if it's about finance, you really want the data to, to to be right. And once they do this review, let them lock the periods, once the so to prevent any further changes and people messing up with already built hours. And the next one, manual export is great, of course, but if you want to move to the next level, use APIs. It's really fairly easy these days to create automatic reports and dashboards. The initial work with setting up automatic reporting will pay off multiple times, and it saves time of people and removes the errors introduced by human factor, which reminds me that I didn't even show dashboards that you can do with reporting, but maybe we will save it for, for a later time. I believe, like, Sevenpase is a good fit. But even if you choose otherwise, any of the top 10 apps will be better than spreadsheets. If you choose a competitor, I would just like you to know if you could send me feedback, like, why, that will really help me, and it will help make seven days even better. Can. I add one more for for that wrap up, Roman? Because there's one more thing that is actually quite important when you have, have to deal with with new applications. That is that you select the marketplace partner that have great support, that are passionate about not just their product, but also to that they understand what you're doing. And that's where Appfire is, world class, I would say. So you are you're really great at that one. So, I think that's also important part to, to actually mention in that selection process. Thank Great. Should we do we have any questions? you. Hey, guys. Thanks, for the great webinar. Yes. We do have a couple of questions that I can go ahead and read out. So I'll start with the first one that we got earlier in the webinar. The question is, can the app be turned on and off per project? I hate to start with with a no, but, yeah, this one is a no. It just lives, in all your projects by default. You cannot turn it off. It doesn't stand in a way, and you can still, like, prevent people from seeing time of others, if if, like, this kind of would be a privacy issue. Right? So you can here in in settings, sorry. Here. Where yeah. Row management. You can just set up that only selected people can see the time. Right? But it's still there in the project. It just doesn't stay in the way. So, no, it's not possible. Okay. The second question is based on custom fields, which you covered earlier, Roman. The question is, are custom fields stored, globally or in the app? Are they stored as. global custom fields? Yeah. Or in the app? Yeah. Yeah. They are stored in the app in seven PACE because they are work log specific. It's not possible to save them on an item because that would be a different granularity level. So they live in the app. Great. And our final question was around big picture. So the big picture integration was mentioned. Can you share how that works again? I can, and we will have more in q one and q two next year, by the way, so just a teaser for this one. But how big picture works is that you may have noticed if I go to personal capacity or maybe I have my team or something like that. Oh, wow. That's nasty. I I wondered why that didn't happen throughout this whole demo, and I think I may know why because I changed the custom fields here. So let's yeah. That's the okay. Can we delete it from the recording, Lisa, afterwards? Anyway, I think it may be because of that. K. Let's let's copy our details. Alright. And we will fix it right after meeting. Anyway, what I wanted to show is oh, okay. That's nasty. I cannot right now. It it it became worse. Why is that? There always has to be one thing that, that is a little bit, Murphy with you. So this is your one moment, Roman. Yes. Yeah. Exactly. Maybe if I just refresh. I just yeah. I'm I'm in a loop, and something is really, like, super off right now. I had problems with my Internet earlier today, but you can hear me, so that's not the issue. Anyway, in times six program, under normal circle senses, you can see, the people capacity. I don't have a screenshot, handy, but imagine, like, seeing here me plus the badge telling me if I was below or above or at, the capacity. That's because we read the information from big picture. So if you have resources and you, like, select capacity for your people, this is what is then displayed in seven days. Then on the, like, other side of the integration in financial module, I already showed the total cost. So this is also how seven pays data or, like, time tracking data in general affect your budgets. And then also, one other part is in Gantt view, in big picture, you can see seven base fields. So in case you need to see how much time was how much billable hours was spent on an item and its children because it can be, like, you know, rolled up. This is what you can see here. So these fields are visible here. But there's more coming if you check, our where is it? Planned. Now we have, like, workload absences and holidays data going to be present in seven days and even more that is not even, covered here yet because it's, like, being baked at the moment. But that's gonna make it even better because resource management and time management are kind of connected in that way. So if you can get one of the the the greatest feature in big picture into seven pays, then, just tell me where to send the money, basically. It's Christmas. Right? I need this. Glad to hear. that. Awesome. Okay. Well, that those are all of our questions. So I think that that concludes our webinar. Thank you guys both so much, and thank you everyone for joining. Thanks a lot. Have a good day. Talk to you soon. good day. Bye. Bye bye.