Facu/Vicky - Adhoc May 8, 2026 2:30 PM (GMT-3)
Summary
El customer journey está casi completo con homepage y secciones definidas. Solo falta la página de servicios, que es accesible desde el nav, desde anuncios o desde el homepage. Se decidió priorizar el contexto antes del precio, evitando que los usuarios accedan directamente al pricing sin entender el valor completo del producto y servicio. Sin embargo, se reconoce la importancia del pricing y se decidió mantener acceso fácil mediante la calculadora.
La homepage incluye una sección de categorías con educación, distribución y comercio, servicios, y manufactura. Cada categoría tiene su título, tag e imagen, y al hacer clic redirige a la página del rubro correspondiente. Se incluye navegación por tareas, métricas, y el proceso de diagnóstico, implementación y mejora.
Se decidió reemplazar los testimonios tradicionales con casos de estudio reales que muestren problemas específicos, soluciones implementadas y resultados con números. Se considera que los testimonios genéricos carecen de credibilidad comparados con casos de uso específicos.
Hay una propuesta de incluir un bloque de integraciones en el homepage con los logos de las principales aplicaciones (WhatsApp, Mercado Libre, Mercado Pago, Tienda Nube, Andriani). Se decidió crear una página separada de integraciones con filtros por categoría para que los usuarios puedan buscar integraciones específicas.
La calculadora fue simplificada para enfocarse solo en el tamaño del equipo y el plan aproximado. El objetivo es mostrar cuánto ahorrará el usuario al implementar el sistema, funcionando como un pricing dinámico. Se necesita definir cómo distinguir entre planes PYME y empresa basándose únicamente en el número de usuarios del sistema, no del tamaño total de la empresa.
Las landing pages de cada categoría se enfocarán 100% en problemas y soluciones específicas para ese rubro. Se decidió no crear landing pages separadas para los sub-rubros (materiales eléctricos, materiales de construcción, artículos de ferretería, etc.) para mantener la gestión manejable. Sin embargo, se mencionarán los sub-rubros en formato carrusel para que empresas específicas reconozcan la experiencia en su campo.
Estructura de las landing pages de categorías:
Se definió que todas las páginas tendrán dos opciones principales: "Agendar diagnóstico" y "Solicitar demo". El flujo llevará al formulario diseñado. Se aclaró que para todos los planes, incluso PYME, los usuarios deberán completar datos antes de agendar la demo.
Para el plan corporativo, se agenda demo directa con más información requerida. Para planes básicos o medio ticket, se prioriza que primero contacten y dejen datos, y luego agenden. Es importante que para cada tipo de plan exista una agenda de citas diferente.
El diseñador trabaja en Cloud Code con un sistema de diseño completo que incluye tokens primitivos, tokens semánticos, colores, tipografía, espaciado, logos, botones, iconos, navegación y cards. Cualquier elemento visual definido se puede agregar al sistema de diseño y se actualizará automáticamente en todas las páginas.
Se puede pasar el diseño directamente desde Cloud Code o desde Figma, facilitando la implementación sin necesidad de compartir archivos de Figma si el equipo usa Cloud Code. Se necesita coordinar con el equipo de IT para la implementación final.
Se recomendó realizar A/B testing de las landing pages dentro de la misma categoría, probando diferentes elementos como ubicación del video vs. caso de estudio, o diseño centrado vs. alineado a la izquierda. Actualmente no se han realizado tests comparativos de diseños porque las intenciones de búsqueda varían entre campañas.
Reunión confirmada para el viernes a las 14:30 para revisar avances con el equipo.
Notes
Transcript
Vicky, how are you?
Yes, how are you? Yes. Buena. Con frío. Sí, no, acá hizo 3 grados a la noche. No, no.
Well, well, well. Let's see. I'm...
You got caught up with the customer journey that they had sent you. Sorry, I'm really heavy with that, but I think it's the most important thing.
No, no Why am I telling you this? I think it's good, I mean, now we already have the homepage, the sections are already defined, then we'll have to retouch copy, but that's the least.
The pricing too. And now the only thing that we would have left for the whole customer journey of the web is the service page. In the homepage we have a direct link. You can access it in different ways. You can access from the nav to the the page of each service, you can access directly via ADD or you can access it from the homepage, right? I don't know if I showed you that.
We hadn't seen it last time at home, we were like...
I'll show it to you quickly so you can also...
This obviously There are things that don't go, these buttons are rounded, they are going to be the real results, obviously.
This button would not actually go, what I would do is request free demo or whatever, or agenda and diagnosis and another one that is to see prices or see rules. We can define that, but more than anything, because you had told me that the pricing page is given a lot of importance, so Yes, the price page was the most clicked one today. I wanted to try to avoid that a little bit, and that they access the price once they have seen something more about us.
Not just the title, the tour and that's it, I see the price like... OK, because it's a product that some plans are expensive. So, seeing it with a little more context and understanding a little more that it is not only the system but also the service and others. So, with that logic, maybe... I don't know if you could see prices because Como justamente evitar un poco que vayan directo al precio. O sea, que sea algo secundario.
I mean, it seems good to me, but you said something key, which is that the problem is not that they go directly to the price, but that they go to the price without context. So, I would also motivate the fact that they go to the pricing, because it will depend to a great extent on the plan they hire. It has to be easy access. I'll tell you that maybe, I don't know if it's the main action we want, but hey.
Here the idea is that a video or an image, ideally a video of the product goes, which is understood by the platform. This is still under review, but what I wanted to show you is this. We have the section of categories. As I scroll, this is education, distribution and commerce, services, manufacturing, and each one has its section with... Your title, your tag and your image. And here you will see, when you click, the idea is that it redirects you directly to the rubric page.
The same from the NAND bar. -Good. -And then we have this, which is what we talked about... by tasks, which is still very good, then the metrics, then we have this part of the process that I had changed a little, I really like how it was, the truth is, so that it is understood that it is...
Yes, diagnostics, implementation, yes, I like it.
The process, these would be like case studies, testimonies, that would be good more than being like case studies, not testimonies The difference between a case study and a testimony is the implementation was great, the team was great, the case study is: I had this problem, I don't know if you read it correctly, but on the page we have a couple of cases of the problem and the solution.
I kind of re-read the testimonies and everything, but I don't know. I already see a testimony and I don't know if they are real or not. Pepito said that the team was divine, I don't care, I just want to know if they had the same problem as me and how they solved it or what they are doing.
At least that you saw a Google testimony, the rest of the things are irrelevant. So, let it be a real case study of numbers, very simple, like they had this problem, we addressed it from this side, the solution was this, the final result was this. Thanks. and the frequently asked questions and this that still We have to define if I would take this out and make it a call to action to put it in the flow.
in the customer journey. That it's not a direct form from here, because we said it was going to be one question at a time.
Of course, yes, like that, that is, to include the issue of the group, the users.
Exactly, yes, yes, that is, I have to put it together right now, but no, anyway, nothing, we go to the...
Great, I'm done, I'm done. Great. Buonissimo. Because I don't know if, let's see, the most important thing is the twist and then comes this. The difference is in the experience, because ad hoc. Yeah. Como que I love it, but I don't know if it gives even more importance to this that people go to the section, to the section page. Yes, that's why I tell you. But I don't know if it's very aggressive too, that's something I had in mind Pero no sé si... is the best or not, you know?
So you want to move it down and the page of the columns appears directly?
Of course.
Oh, yes, yes, that's because it's old. I wouldn't give this much importance. To the order, okay. Yes, that is, to the order is important right now, as if we were making changes, it was outdated. One by one. to use this calculator.
Let's see how that one turned out. I like it.
This one was very... It was very overloaded, which is a lot of information, because in reality, do you remember that we had said that since all this was not necessary, that I clicked it, all this was not going to be, in reality what would remain is only this, the size of the team and the approximate plan and that I can move You see that it is changing, like corporate plan, company plan, PYMEX plan.
All of this, actually, We are not interested in Not that we are not interested, but it is too much information for the person to do. What we want to do is more than anything, tell me how big is the person and how much are you going to save when implementing.
What I'm going to write down What I'm going to write down to finish, like, Maniel, talking to the guys on the team. How to make the distinction between the PYME plan and the company plan only by taking users, if possible, so as not to give wrong information, because it can have four people who are going to use it. There, perhaps, instead of size, the team would be... Personas que van a usar el sistema o una cosa así. Sí, el tamaño del equipo...
Okay. Because a team that is only a commercial team, and in reality it's like the horizontality.
Because...
Now I'm going to do it because I was doing other things. Now my idea was to do it and then I'll show you a video of how it would look.
That is a total And then a block that I feel is missing or that is perhaps going into the solutions is the integrations, which usually draws a lot of attention and is important. Integration with WhatsApp, Tienda Nube, Mercado Libre.
It happens that that is a cross-reference to all or not? Yes. I agree that the integrations are super necessary. Yes, and maybe even put both, both on the homepage and in specific integrations for each section.
Because look, there was a... O sea, viste que la mayoría Most companies usually have an integration block. It's kind of transversal and it's like I also feel that it gives you a little more... Total validity. Yes, validity. Like saying, well, it integrates... Well, this one, I don't know if it's...
I hadn't done that because I also...
Ah, this. .
with these applications that if you want this step comes listed. I think it would be good.
That's what I was going to say, which I think is important to take into account, is if all the integrations are for, as you told me, what integrations are for each plan. Okay.
But I don't know if I would put myself in so much detail. No. Perfect. So, ultimately, in the same call for relevation, if we see that they need this or that integration, they will go for the other plan, but...
How many integrations are there, more or less?
You meet up. There was one. For commercializers, these are the most important ones. Well, and here is missing a new store because it is new, it is not there. But WhatsApp, Andriani, Mercado Pago, Mercado Libre, well, some may be noviar. We have to see if it is convenient to put more or only the most important ones, right?
No, I mean, what I would do is, in the home, I would put the logos of the main ones, these ones, which are the ones that have to be there. And then maybe I would make a list of integrations page and that the person can filter by categories. In fact, I'm going to write it down, which I think is a good idea. page integrations Filters per column. It's a frequent use case, like, let's see if it has this specific integration and look for it.
Like that also adds a lot of value.
Yes, I mean, there, like, I don't know if, like the topic of integrations in itself is a somewhat delicate topic because we don't usually promote integrations a lot, either with other systems or with many applications, like we have developed Esas puntuales que te mencioné, por ejemplo, But when a company comes like "I want to integrate Odoo with my other system because I don't want to migrate the information" No, no, I mean, I was saying that you have it, right?
Ok, ok, because since we don't promote integrations, maybe yes, we give it a lot of importance, it is understood how these do integrations, because it is common in Odoo to do integrations, only that we do not promote it.
What I would do is... I don't know if I would put it as the main link, but within the navigation. Sure, within the blog. Within the blog of categories that you can look for integrations. Because the person who maybe needs a specific solution, it's good that they can access that info.
Yes, or maybe within what is integration, WhatsApp. Maybe a brief description of what you can do with integration.
That's good. If you want, now let's see I want to leave this meeting with the info of each landing of the group. I don't know if you want to share information that I have or we are thinking about it.
Well, if you want I can share it. Um... I had the Figma. Maybe now we can do a match between some things that were left from the home with this that I had. Totally. So I'm going to... El Ciba y ahí te comparto pantalla.
Después, no sé si se puede compartir el... There's the prototype you're building so tomorrow the guys can show it to you and if they have any...
And I'm also going to give you access to the XANA with all the tasks that I'm completing and the ones that remain so that if you want to add something you can do itHorsha.
This is the info I had already thought for the section of categories. Well, identification, the subject of design or visuals, we will see that later, I imagine. But it wasn't something so different from what the landing is, only focused 100% on talking about problems and solutions for that specific group. On the one hand, we have to see howor we mention the sub-groups because you see that today we have within sales companies, we have sales, like we have them very focused on the sub-groups, sales of electrical materials, of construction materials, of hardware articles, of what else was there?
And each of those sub-rules, sorry to interrupt, each of those sub-rules will have its own landing or not?
I vote no. OK. But because also to maintain each page is a mess.
It's a lot of mess and sometimes it's information that is very similar but that changes a little. Yes.
I mean, for now, no. And not for me in the short term, no. I prefer to have good pages of commercial categories, that is, of what we are talking about now.
and then it will be seen, I don't know, but I don't think so. But it would be good to mention them so that if an electrical materials destruction company enters, they know, "Oh look, they already have experience with just my specific field" because perhaps the commercializer is very wide. So yes, see how we include them somewhere, The carousel format as it is now seems great to me.
I'm fine. Like if we were going to make a carousel with a block of info for each type of subgroup. Like maybe I imagine more mentioning them or putting...
Exacto. The Hero video It's a video explaining platform tools. What does that video have? Why should I watch it?
Yes, the idea of making this video here, summary for the group, that is, to be able to show perhaps the video of the home, it will be something more general, talking a little about our value proposition, yes, showing a little of the tool, but that here it is already like a manufacturing company, it carries its process, I mean, that it is more focused, perhaps, on in the specific applications that use those categories.
And then, well, everything, as always, pain and dissolution. A format that I liked. in my day to day. Because we also notice a lot that in the ads or the content that we rate that is of that style, like "with or without Odu", it is what people stay the most looking at and more consume and they are interested, so it would be good to include some block of this type. Um... Well, that And then, Not much more, maybe I could repeat some of the things we saw in the home, put the calculator on it.
I would do it shorter anyway. Yes, that's why. Calculator, integrations and I think I had just put anything else. Oh, and frequent questions. that are very specific to the field. CalculatorConodou, Sinodou, Calculadora, Integraciones, and Frecuentes.
I would put that, that is, it would be... Hero with Video Tour. Mm-hmm. current problems, solution that here in solution it would be good to talk about A little more in detail about the apps of each group, that is, as benefits or features.
Yeah And then, I don't know if you can think of a blog that we saw in the home to add it here, but I would do this well as focusing on problem and solution, that is, that the main thing is that. To repeat it, right? Diagnosis, implementation and improvement.
We don't really test it because, let's see, yes, they have different conversion rates, the landings, but because the intention of looking for a campaign and the landing that is this one, um So the intention of buying and searching for this page is much greater than that of the home, because it is already people who are looking to implement Odoo and are seeing with whom they implement it. So this branding has a really high conversion rate.
Great, great. What was I going to say? I also recommend you, this is more of a personal decision, we don't need to do it now, I recommend you to test, do a b-test of the landings. within the same category, right? I mean, not comparing pears with bananas, but I put one of education and I put one with video and the other I put one with a case study. Or I put it centered and another one on the left. -Something that you have...
And the idea, I'm doing all this in Cloud later, but for the implementation it would be good to talk to your entire IT team.
I'll see how I can pass them to you and make it easier because maybe it's not even necessary to pass the Figma. If you are already using Cloud Code or something similar, I can already pass it from here.
I haven't found it, but I have it loaded in the cloud, in the design system.
In this design system, since I've already put together all the tokens, we have the primitive tokens, which are the colored ones, which are useful for development. The semantic tokens are basically indicating what each color is used for. Then we have For example, the colors that we have in use, we have the typography, we have the spacing, we have examples of Todo. the logos, we have the buttons, etc.
So everything we define as visual elements I can add this here. I can also... I can touch on it, the design system is updated in all the pages. For example, we have icons, we have a navigation bar, then we have cards. Yes. It's a matter of thinking what we want and... And updates the design system, nothing else.
This I pass it Yeah I understand that it's the same as Cloud Code and from Cloud Code to Figma. And from Figma I can design it as And then with integration I can already go and bring it. I have it in Figma and I tell it to implement it in development. Bien.
This is going to be the home, from solutions they will go to each column, from here they will go to each column, the idea is to upload it, and in the same column they will have a component similar to this. So they can... Directly from here, to schedule a demo or with the buttons, the call to action throughout the web. Agenda un diagnóstico y que los va a llevar al al al form que habíamos pensado.
Sí, o sea, la calculadora, acordate que es como un componente más. So that the person finishes deciding, right? That is, it is to unite pricing with something that the person says, well, how much am I going to save and how much is going to come out, right? It's a more dynamic pricing, actually. It's not a new one. Sure, sure. And that, triggers the flow of the form.
Sure, but in this one that you just showed me, can I schedule without completing those data? No. So it's the same thing. Yes, yes. It always has to redirect to the only Al único Forms. Después si...
We continue the same I would leave these two contacts, then we see the way, but Plans basic or maybe half ticket. First contact me and if I'm for an agenda, great. And then the company plan, agenda of the direct demo and I'll have to leave the data.
Then someone from your team will contact them if they didn't schedule it. Leave me your data and that's it. And if you schedule the demo afterwards, great. If not, I'll schedule it for you. That's not a problem. Okay. Okay, okay. What maybe is true is that If the questions from... I mean, the freelance plan, if the questions are not going to be the same for the company plan. So for those who are not sure, maybe that's where it is.
in order to get agendized No, actually when they directly schedule themselves, we may ask even a little more because it's like we're not going to have that instance of round trip and relevation, but a commercial will be added directly. So you have to connect to the demo with a little more information than just the name of the person and the email, because it's like, I blocked an hour or half an hour, whatever the case may be, and I need to know a little more to understand if Perfect.
But do keep in mind that for each type of plan there is a different appointment schedule. When we can separate it and give that link to each plan, great. For example, in pricing or in the calculator.
Did I explain myself? Yes, but I think that the appointments are divided when the person selects the categories.
So, what would be left... What I wanted to assemble is... The landing of the categories, I already have all the information. And build this form to see how it looks. Yes. And then add the integrations part on the homepage. I'll load all of this in Asana.
I'm going to put myself in this position and if I can I'll record a video for you to see it with the team.
And when you can, confirm the IT part.
Yes, I have to see who is going to take the project and that, maybe it would be good directly to coordinate a meeting of 15 minutes Yes, yes, yes, you tell me and I more than anything to know well And what they need. Perfect. Well, Facu, great. Bye Vicky. Thank you very much.
See you on Friday.
Dale, sí, a ver si quedó, no sé si Jack había quedado. No, I don't have the meeting. When do we have it? At 2:30, let's see if...
Yes, I can. At 2:30 I can do it every Friday, so if you want to leave it... In 30 minutes it will be fine.